Virtual knowledge management system

ABSTRACT

It is an object of the present invention to provide a virtual knowledge management system which controls the flow of information relating to the performance of business in an enterprise. The flow of information that is intensively administered by a virtual knowledge base  20  is automatically controlled on the basis of information flow control data  40  including document utilization authorization data, mail communications control data, workflow model data, project data and the like. The utilization of document objects by users is controlled in accordance with the document utilization authorization data. The forwarding of and reply to email messages among users is controlled in accordance with the mail communications control data. The order of work among a plurality of users involved in a certain business process is controlled in accordance with the workflow model data. The flow of information among a plurality of users involved in a certain project is controlled in accordance with the project data. The information flow control data  40  is configurable.

TECHNICAL FIELD

The present invention relates to a virtual knowledge management systemwhich utilizes a computer in order to support the business of anenterprise.

BACKGROUND ART

In a certain universally known business administration system (forexample, see Japanese Patent Application Laid-Open No. 2002-251508), inorder to accomplish efficient management of business that issystematically conducted within an enterprise or between enterprises,the processing deadlines and document forms that are used areadministered for individual work projects, and reports indicating thatprocessing deadlines are growing near, instructions to begin work,document forms that are to be used in the work and the like aretransmitted to the party that is responsible for the work. Furthermore,in this system, in cases where a series of work projects aresuccessively performed by a plurality of persons, and there is a delayin the performance of preceding work projects, the parties responsiblefor the following work projects are notified of this.

Furthermore, another universally known business management system (forexample, see Japanese Patent Application Laid-Open No. 2000-331083) hasa program module called a workflow definition module. This workflowdefinition module stores workflow definitions that indicate combinationsof business processing modules corresponding to the series of processingprocedures and contents of various business projects from the beginningto end of all business projects; a plurality of business processingmodules are combined according to these workflow definitions, andinstructions for the processing that is to be performed next are sent toindividual input-output devices and terminals. The object of this systemis to allow the completely automated performance of business projectswith absolutely no need for work performed by human beings.

Business conducted by one enterprise or by a plurality of enterprisesworking in cooperation is performed by the mutual cooperation orassociation of a plurality of organizations and numerous employeesincluded in the enterprises. Accordingly, in order to conduct businessmore efficiently and increase the productivity of the enterprises, it isimportant to make the mutual cooperation and association of a pluralityof organizations and employees easier and more efficient. For thispurpose, the appropriate control of business-related information, andespecially business-related documents (for example, plans,specifications, circulating documents, accounting documents, designdrawings, photographic images, recorded sound data, movie data,instructions and responses, reports and approvals, various other typesof messages and the like), between organizations or between employees isessential. For example, if information with an appropriate content isprovided at an appropriate time and by an appropriate method fromappropriate organizations or persons to other appropriate organizationsor persons, the association of these organizations or persons isfacilitated and made more efficient, so that productivity is increased.

Furthermore, the scale, organization, environment and the like ofenterprises are constantly changing, and with such changes, the businessof enterprises also changes. In order to maintain a high productivity atall times, the manner of business support such as the abovementionedinformation flow control must vary in a flexible manner in accordancewith changes in business. Furthermore, business configurations also varyaccording to the enterprise involved. If a common business supportingsystem can be applied to different enterprises, the cost of introducingsuch a business supporting system can be kept low. In view of suchfacts, a configurable business supporting system is desired.

From such standpoints, Patent Reference 1 merely provides oneimprovement relating to only some information among business-relatedinformation, i.e., work project deadlines and document forms. The systemdescribed in Patent Reference 2 is a system in which specified businessis performed in a completely automated manner; this system does notimprove the cooperation or association of a plurality of organizationsor persons. Furthermore, neither Patent Reference 1 nor Patent Reference2 provides a configurable business supporting system.

DISCLOSURE OF THE INVENTION

It is one object of the present invention to provide a virtual knowledgemanagement system which is used to control the flow of informationbetween a plurality of organizations or persons participating in abusiness projects, thus facilitating the cooperation and association ofthese organizations or persons.

It is another object of the present invention to provide a configurablebusiness supporting system which can handle changes in the business ofenterprises or differences in the business of different enterprises.

The virtual knowledge management system using a computer according toone aspect of the present invention comprises a virtual knowledge basewhich stores a plurality of objects that are data entities forrespective utilization by a plurality of users, and that belong todifferent object types, and control data that is provided correspondingto each of the abovementioned object types, and that relates to thecontrol of object operations performed by the abovementioned users, anda manager which has a plurality of types of functions for respectivelyperforming a plurality of types of object operations including thedisplay and preparation of the abovementioned objects belonging to eachobject type in accordance with requests from the abovementioned users.The respective functions of the abovementioned manager control therespective operations for the abovementioned objects belonging to therespective object types in accordance with the control data of thecorresponding object types.

In a preferred embodiment, the abovementioned manager further hasfunctions for preparing or altering the abovementioned control datacorresponding to the respective object types in accordance with requestsfrom the abovementioned users.

In a preferred embodiment, the abovementioned control data correspondingto the respective object types includes class definition data whichdefines one or more classes possessed by the abovementioned objectsbelonging to the respective object types, and class security settingdata which defines the classes that can be accessed or that cannot beaccessed by the respective users among the abovementioned one or moreclasses. The abovementioned objects belonging to the respective objecttypes have values of the abovementioned one or more classes defined bythe abovementioned class definition data corresponding to the respectiveobject types. The function used to display the abovementioned objectsinside the abovementioned manager is arranged so that the values ofclasses that can be accessed by the respective users are selected fromthe values of the abovementioned one or more classes possessed by theabovementioned objects belonging to the respective object types, and aredisplayed to the respective users, on the basis of the abovementionedclass security setting data corresponding to the respective objecttypes.

In a preferred embodiment, the abovementioned control data correspondingto the respective object types includes folder definition data whichdefines one or more folders in which the abovementioned objectsbelonging to the respective object types are stored, and folder securitysetting data which defines the folders that can be accessed or thatcannot be accessed by the respective users among the abovementioned oneor more folders. The abovementioned manager further has a folderoperating function which is used to operate the abovementioned one ormore folders defined by the abovementioned folder definition datacorresponding to the respective object types in accordance with requestsfrom the respective users. The abovementioned folder display function isarranged so that folders are displayed with a distinction being madebetween folders that can be accessed and folders that cannot be accessedby the respective users on the basis of the abovementioned foldersecurity setting data corresponding to the respective object types, andso that only folders that can be accessed by the respective users amongthe abovementioned one or more folders that are displayed are opened inaccordance with requests from the respective users.

In a preferred embodiment, the abovementioned control data correspondingto the respective object types includes function security setting datawhich defines functions that can be accessed or that cannot be accessedby the respective users among the abovementioned plurality of types offunctions inside the abovementioned manager. The system is arranged sothat only the functions that are defined by the abovementioned functionsecurity setting data corresponding to the respective object types asbeing accessible by the respective users (among the abovementionedplurality of types of functions for the respective object types insidethe abovementioned manager) can be operated in accordance with requestsfrom the respective users.

In a preferred embodiment, the abovementioned objects belonging to oneof the abovementioned object types are document objects which can beassociated with document files. The respective document objects havetype data which indicates one type selected from a plurality ofspecified types differing in the numbers or types of associated documentfiles. Furthermore, the respective document objects have associationdata which indicates the association with one or more document files incases where the document objects are associated with the abovementionedone or more document files. The function used to display theabovementioned document objects inside the abovementioned managerdisplays the types of the respective document objects on the basis ofthe abovementioned type data of the respective document objects, anddisplays the document files associated with the respective documentobjects on the basis of the abovementioned association data of therespective document objects; furthermore, this function opens theabovementioned associated document files in accordance with requestsfrom the abovementioned users.

In a preferred embodiment, the abovementioned objects belonging to oneof the abovementioned object types are email messages. The respectiveemail messages have type data which indicates one type selected from aplurality of specified types that differ in terms of the presence orabsence of a reply deadline; furthermore, these email messages havedeadline data which indicates the abovementioned reply deadline andstatus data which indicates the status relating to whether or not theabovementioned reply deadline has passed in cases where the emailmessages have the abovementioned reply deadline. The function used todisplay the abovementioned email messages inside the abovementionedmanager is arranged so that this function displays the abovementionedtype data of the respective email messages, and so that this functionalso displays the abovementioned reply deadline and status in caseswhere the respective email messages have the abovementioned replydeadline data and status data.

In a preferred embodiment, the abovementioned objects belonging to oneof the abovementioned object types are email messages. The respectiveemail messages have reply/forwarding control data which relates to thereply to, or forwarding of, the respective email messages. Theabovementioned manager has a reply/forwarding function which is used toreply to the abovementioned email messages, or to forward these emailmessages, in accordance with requests from the abovementioned users. Theabovementioned reply/forwarding function is arranged so that thisfunction controls the reply to or forwarding of the respective emailmessages on the basis of the abovementioned reply/forwarding controldata possessed by the respective email messages.

In a preferred embodiment, the abovementioned objects belonging to oneof the abovementioned object types are business processes whichrespectively have one or more sets of workflow model data thatrespectively define the flow of work among a plurality of users.Furthermore, the abovementioned objects belonging to another one of theabovementioned object types are tasks which have task data that definesthe work that can be performed by the abovementioned users. Furthermore,the abovementioned objects belonging to another one of theabovementioned object types are projects; these respective projects areassociated with one or more of the abovementioned business processes,and with one or more of the abovementioned tasks respectively assignedto one or more of the abovementioned users as defined by the workflowdata of the respective business processes. The abovementioned managerfurther has a project control function which is used to control theprogress of the respective projects in accordance with requests from theabovementioned users. The abovementioned project control function isarranged so that this function prepares and displays a task list thatlists the tasks assigned to the respective users on the basis of theabovementioned one or more business processes and the abovementioned oneor more tasks associated with the respective projects, and so that thisfunction updates the abovementioned task list for the respective usersin accordance with input indicating the initiation or completion oftasks from the respective users.

The virtual knowledge management system according to another aspect ofthe present invention comprises intensive data management means for theintensive management of various types of documents or data that exist inan enterprise, a control data editing part which prepares and altersinformation flow control data involved in the control of the informationflow among a plurality of users, and which registers the abovementionedprepared or altered information flow control data in a memory device,and an information flow control part which uses the abovementionedinformation flow control data registered in the abovementioned memorydevice to control the flow of the abovementioned various types ofdocuments or data among a plurality of user terminals used by theabovementioned plurality of users.

In a preferred embodiment, the abovementioned control data editing partcan prepare and alter utilization authorization data which indicates theauthorization of respective users to utilize the abovementioned varioustypes of documents or data as one type of the abovementioned informationflow control data, and can register the prepared or altered utilizationauthorization data for each user in the abovementioned memory device, inaccordance with requests from specified users. Furthermore, theabovementioned information flow control part can control the utilizationor operation of the respective users with respect to various types ofdocuments or data in the abovementioned data base on the basis of theutilization authorization data for the respective users registered inthe abovementioned memory device.

In a preferred embodiment, the abovementioned control data editing partcan prepare and alter mail communications control data which indicatesdesired limitations regarding the forwarding of, or reply to, emailmessages transmitted from the respective users as one type of theabovementioned information flow control data, and can associate theprepared or altered mail communications control data with email messagestransmitted from the respective users, in response to requests from theabovementioned respective users. Furthermore, the abovementionedinformation flow control part can control the forwarding or replyoperations of the receivers of the respective email messages on thebasis of the communications control data associated with the respectiveemail messages.

In a preferred embodiment, the abovementioned control data editing partcan prepare and alter workflow models relating to desired businessprocesses as one type of the abovementioned information flow controldata, and can register the prepared or altered workflow models in theabovementioned memory device, in response to requests from specifiedusers. Furthermore, the abovementioned information flow control part cancontrol the information flow among a plurality of users involved in therespective business processes on the basis of the workflow models of therespective business processes.

In a preferred embodiment, data relating to the order of work ordocument flow among a plurality of users involved in respective businessprocesses may be included in the abovementioned workflow models relatingto respective business processes. Furthermore, the abovementionedprocess control part can control the order of work or flow of documentsamong a plurality of users involved in the respective business processeson the basis of the abovementioned data relating to the order of work ordocument flow that is contained in the workflow models of the respectivebusiness processes.

In a preferred embodiment, a display part may be further provided whichgraphically displays a hierarchical structure that indicates the mutuallogical relationship between the business processes and one or moreusers involved in each of the business processes on the basis of thedata of the abovementioned workflow models of one or more businessprocesses registered in the memory device.

In a preferred embodiment, the abovementioned control data editing partcan prepare and alter project data relating to projects that include oneor more business processes and one or more tasks as one type of theabovementioned information flow control data, and can register theprepared or altered project data in the abovementioned memory device, inresponse to requests from specified users. Furthermore, theabovementioned information control flow part can control the flow ofinformation among a plurality of users involved in the respectiveprojects on the basis of the project data for the respective projects.

In a preferred embodiment, a display part may be further provided whichgraphically displays a hierarchical structure that indicates the mutuallogical relationships of the projects, one or more business processes ortasks included in each of the projects and one or more users involved ineach of these business processes or tasks on the basis of project datafor the abovementioned one or more projects registered in theabovementioned memory device.

Other objects and advantages of the present invention will become clearfrom the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram which shows an example of the overall hardwareconstruction of a configurable virtual knowledge management systemconstituting one embodiment of the present invention;

FIG. 2 is a block diagram which shows the construction of the solutionsoftware suite;

FIG. 3 is a block diagram which shows in model form an example of thestrengthened or improved functions possessed by the virtual knowledgebase 20;

FIG. 4 shows a concrete example of information email flow control basedon document utilization authorization data;

FIG. 5 is a block diagram which shows a concrete example of email flowcontrol;

FIG. 6 is a block diagram which shows a concrete example of informationflow control based on workflow models and project data;

FIG. 7 is a diagram which shows an example of the GUI window provided bythe workflow manager;

FIG. 8 is a diagram which shows an example of the GUI window provided bythe workflow manager;

FIG. 9 is a diagram which shows an example of the GUI window provided bythe workflow manager;

FIG. 10 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 11 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 12 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 13 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 14 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 15 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 16 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 17 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 18 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 19 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 20 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 21 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 22 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 23 is a diagram which shows an example of the GUI window providedby the workflow manager;

FIG. 24 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 25 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 26 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 27 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 28 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 29 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 30 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 31 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 32 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 33 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 34 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 35 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 36 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 37 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 38 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 39 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 40 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 41 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 42 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 43 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 44 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 45 is a flow chart which shows the procedure whereby the projectmanager prepares a task list;

FIG. 46 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 47 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 48 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 49 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 50 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 51 is a diagram which shows an example of the GUI window providedby the object manager;

FIG. 52 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 53 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 54 is a diagram which shows an example of the GUI window providedby the project manager;

FIG. 55 is a block diagram which shows examples of various types of datainside the virtual knowledge base 20 used by the OM 11, RM 12, WM 13, PM14 and TM 15 for information flow control;

FIG. 56 is a diagram which shows examples of the structures of thedocument class registration data DOC_CLR, document form registrationdata DOC_FMR, and document folder registration data DOC_FLR;

FIG. 57 is a diagram which shows examples of the structures of thedocument class security setting data DOC_CLS, document form securitysetting data DOC_FMS, document function security setting data DOC_FCSand document folder security setting data DOC_FLS;

FIG. 58 is a diagram which shows examples of the structure of thedocument administration table DOC_ADT, annotation administration tableANT_ADT and work list administration table WKL_ADT;

FIG. 59 is a diagram which shows the flow of an example of the controlof the document object operations performed by the OM 11;

FIG. 60 is a diagram which shows an example of the GUI window providedby the OM 11 in order to display document objects;

FIG. 61 is a diagram which shows the flow of an example of the controlfor the purpose of altering the forms of document objects that isperformed by the OM 11;

FIG. 62 is a diagram which shows the flow of an example of the controlof file operations within document objects that is performed by the OM11;

FIG. 63 is a diagram which shows an example of the structure of theemail administration table EML_ADT;

FIG. 64 is a diagram which shows the flow of an example of the controlof email operations that is performed by the RM 12;

FIG. 65 is a diagram which shows an example of the GUI window that isprovided by the RM 12 in order to display email messages;

FIG. 66 is a diagram which shows an example of the structure of theprocess administration table PRC_ADT;

FIG. 67 is a diagram which shows an example of the structure of the taskadministration table TSK_ADT;

FIGS. 68 and 69 are connected diagrams which show an example of thestructure of the project administration table PRC_ADT;

FIG. 70 is a diagram which shows an example of the structure of the tasklist administration table TKL_ADT; and

FIG. 71 is a diagram which shows the flow of an example of the controlof operations relating to tasks within projects that is performed by thePM 14.

BEST MODE FOR CARRYING OUT THE INVENTION

FIG. 1 shows an example of the overall hardware construction of aconfigurable virtual knowledge management system for supporting thebusiness of one or a plurality of enterprises, constituting oneembodiment of the present invention. This virtual knowledge managementsystem may be used within a single enterprise, or may be used in commonby a plurality of collaborating enterprises. Below, a case in which thesystem is used within a single enterprise will be taken as an example inorder to simplify the description.

As is shown in FIG. 1, this virtual knowledge management systemcomprises at least one data base server 1, at least one solution server3, at least one operating log server 5, at least one mail server 7, andat least one web (WWW) server 8, and these servers, 1, 3, 5, 7 and 8 areconnected via a communications network 10 so that mutual communicationis possible. Furthermore, a plurality of user terminals 9 are connectedto the communications network 10, so that these user terminals 9 canaccess the web server 8 and mail server 7. Each of the user terminals 9has a web browser and an email program (not shown in the figures), andcan access the web server 8 and mail server 7. The users are typicallyvarious types of sections (e.g., business section, marketing section,development section, accounting section and the like) or individual firmmembers (including employers as well as employees) within theenterprise; however, organizations and persons outside the enterprisemay also be included among the users. The user terminals 9 are typicallycommunications information processing devices such as personalcomputers, mobile telephones, PDA or the like used by the users.

The data base server 1 administers one or a plurality of data bases 2that exist within the enterprise. Various types of documents that relateto the business of the enterprise (for example, plans, specifications,circulating documents, accounting documents, design drawings,photographic images, recorded sound data, movie data, instructions andresponses, reports and approvals, various other types of messages andthe like) are recorded in each data base 2. Furthermore, data that isused to control the flow of information within this enterprise(hereafter referred to collectively as “information flow control data”)is also recorded in each data base 2. Such information flow control dataincludes various types of data, such as (for example) documentutilization authorization data, workflow model data, project data andthe like.

Document utilization authorization data is data that defines the rightsof respective users to utilize documents (e.g., rights specifying whichoperations are possible (among various types of utilization operationssuch as searching, reading, writing, inputting of annotations,outputting, storage, approval and the like) with respect to whichdocuments and the like). Furthermore, workflow model data is data thatdefines, for each individual business process, work models (e.g., theorder of processing and flow of documents among users in cases where thework is performed by a plurality of users acting in association)indicating which work items (business processes) are to be performed bywhich users (e.g., which sections or which employees) using whichprocedures. Furthermore, project data is data that defines theconstruction of certain projects (e.g., the types of business processesor workflow models that are incorporated into these projects, theassignment of respective business processes or workflow models tosections, the tasks of the respective sections in performing theassigned business processes, the assignment of respective tasks toemployees, the roles of respective employees in performing the assignedtasks and the like).

Such information flow control data is prepared and administered, and (ifnecessary) corrected or deleted, by the solution server 3. Furthermore,the solution server 3 controls the flow of information within thisenterprise on the basis of such information flow control data.

The solution server 3 is the central part of this virtual knowledgemanagement system; a set of computer programs 4 used for businesssupport, which called the “solution software suite” in this description,is installed in this solution server 3. For example, five managerprograms which are respectively called the object manager (OM), reviewmanager (RM), workflow manager (WM), project manager (PM) and managementmanager (AM), as well as several other manager programs not shown in thefigures, are included in the solution software suite 4. By executingthese managers, the solution server 3 not only administers various typesof documents or information existing within this enterprise as in aconventional data base management system, but also controls the flow ofvarious types of documents or information among users so that thecooperation and association of users is facilitated and made moreefficient. Furthermore, the solution server intensively administersvarious types of documents or information within the enterprise on theoverall scale of the enterprise, and controls the flow of thesedocuments or information on the overall scale of the enterprise.Accordingly, even if a plurality of different data bases 2 exist withinthe enterprise, the users can utilize the information in these databases 2 exactly as if this information were information in a single database.

The operating log server 5 administers an operating log 6 comprising loginformation used for the operation of this virtual knowledge managementsystem. The mail server 7 relays the exchange of email messages amongthe users. As will be described later, the exchange of email messagesamong the users is controlled by the review manager (RM) within thesolution suite 4.

The web server 8 is used to provide a graphical user interface (GUI) ofthe solution server 3 (solution software suite 4) to the user terminals9. This GUI is a hypertext format GUI (hereafter referred to as a “webbase GUI”) which can perform displays and operations using the webbrowsers inside the user terminals 9. Accordingly, the users can utilizethe solution server 3 (solution software suite 4) via this web base GUI.

FIG. 2 shows an example of the construction of the abovementionedsolution server 4.

As is shown in FIG. 2, the solution software suite 4 has (for example)five manager programs, i.e., an object manager (OM) 11, review manager(RM) 12, workflow manager (WM) 13, project manager (PM) 14 andmanagement manager (AM) 15. Examples of respective typical functions ofthese five managers 11 through 15 may be described as follows:

The object manager (OM) 11 intensively manages documents of variousformats and types existing within the enterprise throughout theenterprise as a whole. As a result, various types of documents withinthe enterprise can be effectively utilized by various sections oremployees within the enterprise. Furthermore, the OM 11 can not onlyadminister individual documents in file units, but can also administer aplurality of documents combined as single unit objects; furthermore,there are a plurality of different types of document objects that differin terms of the types of documents that are combined. Furthermore, theOM 11 also controls the manner in which various sections or employeeswithin the enterprise utilize various types of documents within theenterprise (e.g., searching, reading, writing, inputting of annotations,approval, outputting, distribution, storage or the like) in accordancewith the document utilization rights possesses by the respectivesections or employees. As a result, documents that are necessary oruseful to the abovementioned sections or employees (among the vastnumber of documents existing within the enterprise) are automaticallyselected and provided for the utilization of the sections or employees.Furthermore, in cooperation with a project manager (PM) 14 to bedescribed later, the OM 11 also has the function of notifying sectionsor employees participating in various types of projects within theenterprise of the tasks that are to be performed by these sections oremployees in accordance with the state of progress of these projects.

The review manager (RM) 12 controls the distribution of email messagesamong various sections or employees within the enterprise. For example,various types of control are possible, such as classification of emailmessages into a plurality of types and control of the flow of email bydifferent methods according to each type, management of reply deadlinesfor respective email messages, and control as to whether or not theforwarding of respective email messages and distribution of copies ispossible. Furthermore, the RM 12 also performs control operationsrelating to communications and the exchange of documents between varioussections or employees within the enterprise and the document printingroom and document storage room. Moreover, the RM 12 also performscomprehensive tracking of the utilization status of documents within theenterprise.

The workflow manager (WM) 13 has the functions of preparing workflowmodels that express the manner of pursuing various types of work(business processes) within the enterprise, and registering the data ofthe workflow models of the respective business processes in the database 2. The workflow model data for the respective business processesincludes information indicating which sections or which employees areresponsible for the business processes, what types of documents are usedin the business processes, and the order in which work is performed ordocuments are forwarded by the responsible sections or employees. Theaddition of new workflow models, upgrading of the versions of existingworkflow models and the deletion of existing workflow models can beperformed by a simple method. The workflow models prepared for variousbusiness processes by the WM 13 are incorporated into various projectsand used to control the progress of these respective projects by theproject manager (PM) 14 described next.

The project imager (PM) 14 has the functions of preparing projects inwhich various types of business processes are combined, and registeringthis project data in the data base 2. The respective sets of projectdata include detailed information indicating which business programs areincluded in the projects, what kinds of tasks are assigned to thesections or employees involved in the business processes, and what rolesare played by respective employees (for example, analysts, designers,system engineers or the like) in the respective tasks. Furthermore, thePM 14 also notifies the sections or employees involved in such projectsof the detailed information relating to these projects. Moreover, the PM14 monitors the progress of business processes included in the projects,and provides appropriate documents or reports corresponding to thisprogress to the sections or employees involved in the businessprocesses. In this way, the progress of the projects is controlled. Byusing the PM 14, the creation of new projects, the upgrading of theversions of existing projects and the deletion of business projects canbe accomplished in a simple manner.

The administration manager (AM) 15 has the function of registeringvarious types of data (hereafter referred to as “operating data”) usedfor the overall operation or control of this virtual knowledgemanagement system. For example, the registration of users, the settingof document utilization authorization for users, the setting of varioustypes of document forms, the setting of various types of search forms,the setting of GUI forms and the like can be performed using the AM 15.The preparation of new operating data, the modification of existingoperating data, the deletion of existing operating data and the like canbe accomplished in a simple manner.

As a result of the functions of the abovementioned managers 11 through15, not only are various types of documents and information within theenterprise simply managed in the data base 2, but the flow of varioustypes of documents or information between sections or between employeesis also controlled so that the performance of business is supported.Furthermore, even if a plurality of data bases 2 exist within theenterprise, the documents or information in such a plurality of databases 2 can be handled in an intensive manner. Moreover, the manner inwhich the flow of information is controlled can be flexibly varied inaccordance with the circumstances of the enterprise. Thus, the functionof the data base 2 of the enterprise is strengthened or improved by thefunctions of the managers 11 through 15 so that this data base 2 cancontribute much more efficiently to the performance of business. Thevirtual knowledge base 20 shown in FIG. 2 indicates a data base that hasthus been strengthened or improved. Furthermore, the construction andfunctions of this virtual knowledge base 20 can be flexibly arranged inaccordance with variations in the business content of the enterprise orthe environment in which the enterprise is placed, or in accordance withcircumstances that vary for each enterprise. In other words, thisvirtual knowledge base is configurable. All types of users (sections oremployees) 10 within the enterprise can perform various types of workusing this configurable virtual knowledge base 20.

FIG. 3 shows (in model form) an example of the strengthened or improvedfunctions of the virtual knowledge base 20.

As is shown in FIG. 3, various types of documents 30 prepared or editedby various sections (e.g., business section, development section, designsection, service section and the like) or various employees (e.g., Mr.A, Mr. B, Mr. C, Mr. D and the like) within the enterprise areintensively administered by the virtual knowledge base 20. Furthermore,the flow of these various types of documents 30 among sections or amongemployees is automatically controlled on the basis of the abovementionedvarious types of information flow control data (e.g., documentutilization authorization, workflow models, project data and the like)40. As a result, shared use and effective utilization of the documentsare promoted on the scale of the enterprise.

Several concrete examples of such information flow control will bedescribed below.

FIG. 4 shows the example of information flow control based on documentutilization authorization.

As is shown in FIG. 4, a plurality of employees, e.g., “Mr. A” 51 and“Mr. B” 52 and the like, are present in the enterprise in question. Asis indicated by the arrows 106, the system administrator 57 of theenterprise can appropriately create document utilization authorizationdata for each of the employees such as “Mr. A” 51, “Mr. B” 52 and thelike (e.g., folder security setting data 53 and 54 relating tolimitations on the utilization of folders, function security settingdata 55 and 56 relating to types of utilization behavior and the like)using the administration manager (AM) 15, and can register this data inthe data base. Furthermore, using the administration manager (AM) 15,the administrator 57 can also perform editing such as modification,correction, addition, deletion or the like of document utilizationauthorization data as necessary.

In the example shown in the figures, it is defined in the foldersecurity setting data 53 for “Mr. A” which folders can be utilized by“Mr. A” 51 (e.g., “#A” and “#B”) and which folders cannot be utilized by“Mr. A” 51 (e.g., “#C”) among the folders contained in the data base(e.g., “#A”, “#B” and “#C”). Furthermore, it is defined in the foldersecurity setting data 54 for “Mr. B” which folders can be utilized by“Mr. B” 52 (e.g., “#A”, “#B” and “#C”) and which folders cannot beutilized by “Mr. B” 52 (e.g., none) among the folders contained in thedata base (e.g., “#A”, “#B” and “#C”).

In the example shown in the figures, furthermore, it is defined in thefunction security setting data 55 for “Mr. A” which types of utilizationbehavior can be performed by “Mr. A” 51 with respect to the folders(e.g., reference) and which types of utilization behavior cannot beperformed (e.g., addition, modification, revision and deletion), as wellas which types of utilization behavior can be performed by “Mr. A” 51with respect to the document objects (for example, documents or sets ofdocuments) (e.g., addition, revision and reference) and which types ofutilization behavior cannot be performed (e.g., modification anddeletion). Furthermore, it is defined in the function security settingdata 56 for “Mr. B” which types of utilization behavior can be performedby “Mr. B” 51 with respect to the folders (e.g., addition, modification,revision, reference and deletion) and which types of utilizationbehavior cannot be performed (e.g., none), as well as which types ofutilization behavior can be performed by “Mr. B” 52 with respect to thedocument objects (for example, documents or sets of documents) (e.g.,addition, modification, revision, reference and deletion) and whichtypes of utilization behavior cannot be performed (e.g., none).

The object manager (OM) 11 can allow various document objects within thedata base to be utilized by each of the employees such as “Mr. A” 51,“Mr. B” 52 and the like. In this case, the OM 11 controls theutilization behavior of the respective employees with respect to thedocument objects in accordance with the document utilizationauthorization data 53, 54, 55 and 56 for the respective employees thathas been registered beforehand by the administrator 57. For example, theOM 11 limits the document folders that can be utilized by the employeeson the basis of the folder security setting data for the respectiveemployees. Furthermore, for example, the OM 11 limits the types ofutilization behavior of the employees with respect to folders or objectson the basis of the function security setting data for the respectiveemployees.

In the example shown in the figures, the document folders “#A” 61, “#B”62 and “#C” 63 are present in the data base. As is indicated by thearrows 101 and 102, the OM 11 allows only the utilization of thedocument folders “#A” and “#B”, and prohibits the utilization of thedocument folder “#C”, in the case of “Mr. A” 51 in accordance with thefolder security setting data 53 for “Mr. A”. On the other hand, as isshown by the arrows 103, 104 an 105, the OM 11 allows the utilization ofall of the document folders “#A”, “#B” and “#C” in the case of “Mr. B”52, in accordance with the folder security setting data 54 for “Mr. B”.

In this case, the system can be arranged so that (for example) thedocument folders that can be utilized and the document folders thatcannot be utilized by each employee are displayed in different colors orconfigurations on the screen of the user terminal of each employee, orso that only the folders that can be utilized are displayed.Alternatively, the system can be arranged so that among the documentfolders that are displayed on the screen of the user terminal of eachemployee, the document folders that can be utilized by the employee canbe opened, while the document folders that cannot be utilized cannot beopened.

Furthermore, in the example shown in the figures, the OM 11 allows “Mr.A” 51 only to make reference to the utilizable document folders “#A” and“#B”, and prohibits any additions, modifications, revisions or deletionswith respect to these document folders, in accordance with the functionsecurity setting data 55 for “Mr. A”. Furthermore, the OM 11 allows “Mr.A” 51 to make only additions, revisions or references to the objectswithin the utilizable document folders “#A” and “#B”, and prohibits anymodifications or deletions with respect to these document folders, inaccordance with the function security setting data 55 for “Mr. A”. Onthe other hand, in accordance with the function security setting data 56for “Mr. B”, the OM 11 allows “Mr. B” 52 to make additions,modifications, revisions, references and deletions with respect to theutilizable document folders “#A”, “#B” and “#C”, and also allowsadditions, modifications, revisions and deletions to be made withrespect to the objects within these document folders.

Such control relating to the utilization of information within theenterprise by the respective employees is performed throughout theentire enterprise. Instead of such control, or in combination with suchcontrol, it would also be possible to control the utilization ofinformation by sections (i.e., by respective groups) using a similarmethod. As a result of such control of the flow of information beingperformed on the scale of the enterprise, appropriate documents orinformation can be selected from the vast quantities of various types ofdocuments or information existing within the firm, and can be suppliedfor the utilization of appropriate sections or employees.

Furthermore, the OM 11 administers various types of documents within thedata base using logical entities of document data called documentobjects. There are a plurality of types of document objects; differenttypes of document objects are indicated for example as document objects71 through 76 inside the document folder “#B” 62 in FIG. 4.Specifically, for example, there are document objects of different typessuch as single sheet (SS) objects 71, multi-sheet (MS) objects 72,multi-document (MD) objects 73, multi-representation (MR) objects 74,annotation (AN) objects 75, registered (RG) objects 76 and the like.Furthermore, the OM 11 can also handle objects called work lists (WKL)77, which are sets of other pluralities of document objects. In FIG. 4,for convenience of graphic illustration, only one of each type ofdocument object is shown; however, it goes without saying thatpluralities of document objects of any of the abovementioned types maybe present.

The single-sheet (SS) objects 71 have object definition data 81; thisobject definition data 81 is associated with a single document file 82that expresses a single sheet. The multi-sheet (MS) objects 72 haveobject definition data 83; this object definition data 83 is associatedwith a single document file or a set 84 of a plurality of document filesexpressing a plurality of sheets. For example, a document file such as asingle independent design drawing is suitable for handling as an SSobject 71. On the other hand, for example, a document file comprising aplurality of sheets that are more conveniently managed as a unifiedentity, such as a plurality of partial drawings obtained by splitting asingle large drawing, is suitable for handling as a single MS object. Inthe case of document files 82 and 84 which are handled as a single sheet(SS) object 71 or multi-sheet (MS) object 72, it is not necessary thatthe document file 82 or 84 be present in the same folder as the singlesheet (SS) object 71 or multi-sheet (MS) object 72 itself; thesedocument files may be present in any location within the virtualknowledge base 20, including the personal computers used by the users.

Multi-document (MD) objects 73 have object definition data 85; thisobject definition data is associated with a set 86 comprising aplurality of document files with different information. For example,document files with different information more conveniently managed as aunified entity, such as image files, tabular calculation files and DTPfiles that respectively express a photograph, parts and description of asingle product, are suitable for handling as a single MD object. Such adocument file 86 that is handled as a multi-document (MD) object 73 neednot be present in the same folder as the multi-document (MD) object 73itself; this document file 86 may be present in any location within thevirtual knowledge base 20, including the personal computers used by theusers.

Multi-representation (MR) objects 74 have object definition data 87;this object definition data 87 is associated with a set 88 comprising aplurality of document files of different formats. For example, documentsof different formats with the same information that can be moreconveniently managed as a unified entity, such as CAD files, rasterimage files and page description language files of the same designdrawings, are suitable for handling as a single MR object. Such adocument file 88 that is handled as a multi-representation object (MR)74 need not be present in the same folder as the multi-representation(MR) object 74 itself; this document file 88 may be present in anylocation within the virtual knowledge base 20, including the personalcomputers used by the users.

Annotation (AN) objects 75 have object definition data 90; this objectdefinition data 90 accompanies some other document object 91, and isassociated with a document file or document file set 92 that expressesthe content of the annotation. For example, a sound data file thatrecords a certain meeting is suitable for handling as an AN object thataccompanies a document object describing the minutes of this meeting.Such a document file 92 that is handled as an annotation (AN) object 75need not be present in the same folder as the document object 91 itselfthat is accompanied by the annotation (AN) object 75; this document file92 may be present in any location within the virtual knowledge base 20,including the personal computers used by the users.

Registered (RG) objects 76 have only object fixed definition data 89;these are document objects that do not yet have an actual document fileassociated with this data, but that are formally recorded in the database for the time being. Subsequently, RG objects 76 can be convertedinto one of the object types described above by being associated with acertain document file.

Work lists (WKL) 77 have object definition data 93, and this objectdefinition data 93 is associated with one or a plurality (ordinarily aplurality) of other document objects (e.g., the document objects 72 and73 in the example shown in the figures). For example, a plurality ofdocument objects used to perform a certain work project are suitable forhandling as a single work list (WKL). The plurality of document objects83 and 85 handled as the work list (WKL) 93 need not be present in thesame folder; these document objects may be present in any locationwithin the virtual knowledge base 20.

As is shown for example in FIG. 4, all of the document objects 71, 72,73, 74, 75, 76 and 77 have object definition data 81, 83, 85, 87 89, 90or 93 including type discriminators that indicate the type of thedocument object. The OM 11 discriminates the types of the documentobjects 71, 72, 73, 74, 75, 76 and 77 on the basis of the typediscriminators within the object definition data 81, 83, 85, 87, 89, 90and 93. Furthermore, when the OM 11 displays symbols (e.g., icons) ofthe document objects 71, 72, 73, 74, 75, 76 and 77 on the screens of theuser terminals of the employees, the OM 11 can use symbols with designsthat are peculiar to the respective types of these document objects.Furthermore, when the OM 11 displays the contents of objects thatcombine a plurality of document files or a plurality of document objectsas in the case of MS, MD, MR, AN or WKL, the OM 11 can simultaneously orsuccessively display the contents of the plurality of document files ordocument objects that are associated with these objects.

FIG. 5 shows a concrete example of email flow control.

As is shown in FIG. 5, a plurality of employees such as (for example)“Mr. A” 111, “Mr. B” 112 and “Mr. C” 113 are present in the enterprise.The email messages that are exchanged by these employees include aplurality of different types of email messages. For example, there arethree types of mail, i.e., formal mail (FM), informal mail (IFM) andbulletin mail (BM). In the case of FM, various types of communicationscontrol settings (e.g., settings relating to reply deadlines, permissionfor forwarding, communication group limitations and the like) can be setin a detailed manner. In the case of IFM, communications controlsettings cannot be set as finely as in the case of FM. BM is mail whichonly transmits information (i.e., mail to which no reply can be made);for example, such mail is used in applications such as the distributionof company reports or the like.

As is indicated by the arrow 158, the system administrator 114 of theenterprise can use the administration manager (AM) 15 to create suitableforms for respective types of email in accordance with the circumstancesof the enterprise, and to register these forms in the data base. Here,the term “email forms” refers to the written forms of indexes that areused when sets of information items that are selected from variousinformation items contained in the email beforehand (and that aredisplayed in the display of email information) are displayed, i.e., whenemail information is displayed. The types of communications controlsettings that can be made depend on this form. In the example shown inthe figures, two types of forms “F#1” and “F#2” have been created for FMuse, one type of form “IF#1” has been created for IFM use, and one typeof form “B#1” has been created for BM use. Furthermore, using theadministration manager (AM) 15, the administrator 114 can performediting of mail forms, such as modifications, corrections, deletions andthe like, as required.

Mail boxes (MB) 121, 131 and 132 are provided for respective employeessuch as “Mr. A” 111, “Mr. B” 112, “Mr. C” 113 and the like. Separatemail folders for the abovementioned mail types (i.e., FM, IFM and BM)are provided in association with the mail boxes of the respectivepersons, as is indicated in the figures by the FM folder 122, IFM folder123 and BM folder 124 shown in association with the MB 121 of “Mr. A”.

The review manager (RM) 12 provides a function that creates emailmessages of arbitrary types using arbitrary mail forms for therespective employees, and transmits these email messages to arbitraryaddresses. Furthermore, the review manager (RM) 12 provides a functionthat stores email messages that have been addressed and transmitted tothe employees in the mail boxes of these employees, and that displaysthe received mail in these mail boxes to the employees (arrows 151, 155and 157). In this case, the review manager (RM) 12 distinguishes thetypes of the received mail, and stores the received mail in the mailfolders corresponding to these types. Furthermore, for each employee,the review manager (RM) 12 provides the function of controlling theforwarding of and reply to received mail on the basis of communicationscontrol settings assigned to the received mail.

For example, let us assume that “Mr. C” 113 creates formal mail (FM) 125using the FM form “FM#1” 142, and transmits this mail to “Mr. A” 111, asindicated by the arrow 158 in FIG. 5. In this case, let us assume thatin the FM 125, “Mr. C” 113 has set the reply deadline as “Apr. 1, 2002”,and has set the forwarding approval (AF) as “ON”, and the communicationgroup limitation (LM) as “ON”. In this case, when the RM 12 displays theFM 125 to “Mr. A” 111, who is the receiver of the FM 125, the RM 12displays the reply deadline of “Apr. 1, 2002”, and indicates whether ornot “Mr. A” 111 has replied to this FM 125. Moreover, in cases where“Mr. A” 111 has not yet replied, the RM 12 monitors whether or not thedeadline of “Apr. 1, 2002” has passed, and displays the results of thismonitoring using (for example) a colored symbol or the like.

Furthermore, in the case of the abovementioned example, since thesetting for forwarding approval (AF) of the FM 125 is “ON”, the RM 12controls the system so that “Mr. A” 111 cannot forward the FM 125 toother addresses (for example, the system is set so that the menu item of“forward” on the display screen of the FM 125 cannot be operated).

Furthermore, in the case of the abovementioned example, since thesetting of the communication group limitation (LM) of the FM 125 is“ON”, the RM 12 limits the addresses of the reply mail only to “Mr. C”111, who was the transmitter of the FM 125, and to the address that wasthe destination of the FM 125, in cases where “Mr. A” 111 attempts totransmit a reply mail for the FM 125. For example, if “Mr. C” 111transmitted the FM 125 to only two persons, i.e., “Mr. A” 111 and “Mr.B” 112, then the possible addresses for the reply mail to FM 125 islimited to a group of three persons, i.e., “Mr. C” 111, “Mr. A” 111 and“Mr. B” 112 (accordingly, only replies indicated by the arrows 153 and154 are possible), and reply mails cannot be sent to other addresses.

Meanwhile, in the case of the other FM 126 shown as an example in FIG.5, since the setting of the forwarding approval (AF) is “OFF”, “Mr. A”111 can forward the FM 126 to other addresses. Furthermore, in the FM126, since the setting of the communication group limitation (LM) is“OFF”, “Mr. A” 111 can send reply mails to the FM 126 to arbitraryaddresses.

As a result of the abovementioned email communications control,important confidential email messages can be prevented from beingerroneously sent to inappropriate addresses.

FIG. 6 shows a concrete example of information flow control based onworkflow model data and project data.

As is shown in FIG. 6, there are a plurality of sections such as“Section A” 161, “Section B” 164, “Section C” and “Section D” in theenterprise in question. For example, a plurality of employees such as“Mr. A” 162, “Mr. B” 163 and the like belong to “Section A” 161;furthermore, for example, a plurality of employees such as “Mr. C” 165,“Mr. D” 166 and the like belong to “Section B” 164. In addition, thereare also employees such as the system administrator 167, a “Mr. X” 168who has the authority to create workflows, and a “Mr. Y” 169 who has theauthority to create projects.

Using the administration manager (AM) 15, the system administrator 167can register information for sections and employees present in theenterprise, forms of various types of documents used in this enterpriseand the like in the data base as indicated by the arrows 204. Here, theterm “forms of documents” refers to the written forms of indexes thatare used when sets of information items that are selected from variousinformation items contained in document objects beforehand (and that aredisplayed in the display of document objects) are displayed, i.e., whenthe information of document objects is displayed. In the example shownin the figures, information relating to “Section A” 161 and “Mr. A” 162and “Mr. B” 161 who belong to this section is registered as “Section A”employee data 173; furthermore, information relating to “Section B” 164and “Mr. C” 165 and “Mr. D” 166 who belong to this section is registeredas “Section B” employee data 174. Furthermore, the forms 171 and 172 ofvarious types of documents such as “form A”, “form B” and the like arealso registered. Using the AM 15, the system administrator 167 canperform (as required) editing such as modifications, corrections,deletions or the like with respect to arbitrary section and employeeinformation, the forms of various types of documents and the like thathave been registered.

Using the workflow manager (WM) 13, “Mr. X” 168, who has the authorityto create workflows, can create workflow models for various arbitrarybusiness processes, and can register these workflow models in the database, as indicated by the arrows 205. In the example shown in thefigures, workflow models 175, 178 and 179 for a plurality of businessprocesses such as “PROC1”, “PROC2”, “PROC3” and the like are registered.Here, as is indicated for example with respect to the workflow model 175for “PROC1”, a flow of work or documents between sections in thebusiness process, as created by “Mr. X” 168 (hereafter referred to asthe “process information flow”) 176, and a designation of the documentsused in reports between sections, as designated by “Mr. X” 168(hereafter referred to as the “report document designation”) 177, areincluded in the workflow model for each business process. For example,in the “PROC1” workflow model 175, the process information flow 176defines a flow of work or documents which starts with “Section A”, isthen transferred to “Section B” and “Section C”, and finally convergesand ends in “Section D”, is defined. Furthermore, the report documentdesignation 177 of the “PROC1” workflow model defines the fact that twotypes of documents, i.e., “documents A” and “documents B”, are used inthe reports among the sections. If necessary, “Mr. X” 168 can use the WM13 to perform editing such as modifications, corrections, deletions andthe like with respect to the workflow models of the registered arbitrarybusiness processes.

Furthermore, using the workflow manager (WM) 13, “Mr. X” 168 can createvarious arbitrary tasks (tasks are more detailed work entities that areconstituent elements of business processes) 198, and can register thesetasks 198 in the data base, as indicate by the arrows 205. Furthermore,although this is not shown in the figures, “Mr. X” 168 can also createvarious sub-tasks (sub-tasks are even more detailed work entities thatare constituent elements of tasks) under the respective tasks registeredbeforehand, and can register these sub-tasks in the data base. Othereven more detailed sub-tasks can also be created under the respectivetasks, and can be registered in the data base. Thus, the data ofrespective tasks can be created as tree-form hierarchical structures ofthe data of various sub-tasks, and can be registered in the data base.If necessary, “Mr. X” 168 can use the WM 13 to perform editing such asmodifications, corrections, deletions and the like with respect to theregistered arbitrary tasks or sub-tasks. The creation, registration andediting of arbitrary tasks and sub-tasks can also be accomplished usingthe project manager (PM) 14 instead of the WM 13.

Using the project manager (PM) 14, “Mr. Y” 169, who has theauthorization to create projects, can create data of various arbitraryprojects, and can register these projects in the data base, as shown bythe arrow 203. In the example shown in the figures, the project data 183of a single project called “PROJ1” is registered. Here, as is shown forexample with respect to the project data 183 for “PROJ1”, one or aplurality of business process designations 184 and 197 constituting theprojects designated by “Mr. Y” 169 are included in the project data ofthe respective projects. For example, designations 184 an 197 for thetwo business processes “PROC1” and “PRPC2” are included in the projectdata 183 for “PROJ1”.

On the basis of the business process designations 184 and 197 from “Mr.Y” 169, the PM 14 associates the work flow models 175 and 178 of thedesignated business processes “PROC1” and “PROC2” with the project data183 of this project “PROJ1”. Furthermore, utilizing the abovementionedassociation, the PM 14 automatically prepares report document forms 105and section data 189, 194, 195 and 196 for each of the designatedbusiness processes “PROC1” and “PROC2” with the project data for thisproject “PROJ1”. For example, in the case of the business process“PROC1”, a report document form 185 which includes the “document A” form186 (a copy of the “document A” form 171) and the “document B” form 187(a copy of the “document B” form 172), and section data 189, 194, 195and 196 for the four sections “Section A”, “Section B”, “Section C” and“Section D” that are involved in the business process “PROC1”, areautomatically prepared by the PM 14 on the basis of workflow model 175for “PROC1”.

Furthermore, when the project “PROJ1” is created, “Mr. Y” 169 can setthe work schedules 191 for the sections, the assignment 192 of tasks foreach stage of the work to the sections (arbitrary tasks can be selectedfrom the various tasks 198 registered by the WM 13, and can be assignedto the sections), and the assignment 193 of roles to the employeeswithin the sections, as the concrete contents of each set of sectiondata 189, 194, 195 and 196 relating to the respective business processeswithin the project data 183. In the example shown in the figures, forexample, the planned starting date of “Apr. 1, 2002” and the plannedcompletion data of “Sep. 1, 2002” are set in the work schedule 191 asthe concrete content of the section data 189 of “Section A” for thebusiness process “PROC1”. Furthermore, in the task assignments 192, forexample, “task 1” (e.g., analysis of demand) is assigned to “stage 1”(e.g., the initial stage within the overall work period), “task 2”(e.g., overall design) and “task 3” (e.g., part design) are assigned to“stage 2” (e.g., the intermediate stage within the overall work period),and “task 4” (e.g., prototype testing) is assigned to “stage 3” (e.g.,the final stage within the overall work period). Moreover, in the roleassignments 193, for example, “Mr. A” is assigned to “role 1” (e.g.,analyst), and “Mr. B” is assigned to “role 2” (e.g., system engineer).When “Mr. Y” 169 sets the role assignments 193, the PM 14 automaticallydisplays a list of the employees belonging to the respective sections onthe basis of the employee registration data 173 and 174; accordingly,the setting work of “Mr. Y” 169 is facilitated. If necessary, “Mr. Y”169 can use the PM 14 to perform editing such as modifications,corrections, deletions and the like with respect to the registeredproject data 183.

On the basis of the registered project data 183, the PM 14 creates tasklists 181 and 182 which list various jobs that are to be processed foreach of the sections 161 and 164, as indicated by the arrows 200. Forexample, as is shown in the figures, task lists for all of the sectionsinvolved in the registered project, such as a task list 181 for “SectionA”, a task list 182 for “Section B” and the like, are created. Forexample, various jobs that have been assigned to “Section A” 161 on thebasis of the registered project data 183 are listed in the task list 181for “Section A”. For instance, the first line expresses the job that isto be performed by the employee of “role 1” in “task 1”, the second lineexpresses the job that is to be performed by the employee of “role 2” in“task 1”, the third line expresses the job that is to be performed bythe employee of “role 1” in “task 2”, and the fourth line expresses thejob that is to be performed by the employee of “role 2” in “task 2”.Although this is omitted from the figures, jobs relating to other taskssuch as “task 3”, “task 4” and the like are also similarly listed inthis list 181. Schedules (planned starting data and planned completiondate), progress (whether or not the actual starting date or completiondate is behind schedule or the like), names of stages, names of businessprocesses and the like are also displayed in the task lists 181 and 182.

The PM 14 can list all of the jobs assigned to the sections in the tasklists 181 and 182 for the respective sections; instead, however, itwould also be possible to arrange the system so that jobs that have notyet been started by the sections are not listed (in accordance with theprogress of the business processes). For example, in the case of thebusiness process “PROC1” of the project “PROJ1”, the work of “Section B”is performed after the work of “Section A”, as defined in the workflowmodel 175 for “PROC1”. Accordingly, the job in “Section B” cannot bestarted until the job in “Section A” is completed. As will be describedlater, the PM 14 monitors the progress of the respective jobs in therespective sections, and records which jobs have been started orcompleted. For example, the system can be arranged so that the OM 11does not show the jobs in “Section B” that follow the jobs in “SectionA” in the task list 182 for “Section B” while these jobs in “Section A”have not yet been completed, and shows these following jobs in the tasklist 182 for “Section B” at the point in time at which the jobs in“Section A” have been completed, on the basis of the job progressmonitoring results obtained by this PM 14.

The OM 11 can provide the task lists for the respective sections cratedby the PM 14 as described above to the employees of these sections. Forexample, as is shown by the arrow 201, the OM 11 can display the tasklist 181 for “Section A” on the screens of the user terminals of theemployees 162 and 163 of “Section A” 161; furthermore, as is shown bythe arrow 202, the OM 11 can display the task list 182 for “Section B”on the screens of the user terminals of the employees 165 and 166 of“Section B” 164.

Each employee can select the jobs that are to be performed by thisemployee himself from the task list that is displayed on the screen ofhis own user terminal. When a given employee selects a given job fromthe task list, the PM 14 judges that the performance of this job hasbeen begun by this employee, and sets the date at this time as theactual starting date of the job. Furthermore, using the PM 14, eachemployee can open the report form 185 regarding the job selected by theemployee himself (i.e., the job performed by the employee himself), andcan create a work report for employees responsible for following jobs byentering arbitrary comments into this report form 185. When the creationby this employee of a work report relating to this job is completed, thePM 14 judges that the job has been completed, and stores the work reportthat has been created by this employee (i.e., the report form 165 inwhich the comments of the employee have been inserted). As was alreadydescribed above, the OM 11 shows the jobs that follow the complete jobin the task lists for the other sections to which these following jobshave been assigned. When a given employee selected such as following jobfrom such a task list for another section, the PM 14 judges that thisfollowing job has been started. Furthermore, using the PM 14, theemployee who has selected this following job can open the report form185 in which comments of preceding employees concerning this job havealready been entered, and can read these comments of precedingemployees, or can create a report to employees responsible for furtherfollowing jobs by additionally entering his optical waveguides comments.For example, when “Mr. A” 162 an “Mr. B” 163 of “Section A” 161 havecompleted their own respective jobs, these employees open the reportform 185, and enter their own respective comments as indicated by thearrow 206. Subsequently, when “Mr. C” 165 and “Mr. D” 166 of “Section B”164 perform following jobs, these employees open the report form 185,read the comments of “Mr. A” 162 and “Mr. B” 163, and then enter theirown comments, as indicated by the arrow 207. Thus, the report form 185containing comments from persons in “Section A” 161 and “Section B” 164constitutes a report to persons in “Section D” who are responsible forfurther following jobs.

In the information flow control described above, section-to-sectionworkflow models are utilized; however, information flow control amongshift groups or among employees can also be accomplished by usingworkflow models among shift groups in shift work, workflow models amongindividual employees or the like.

As a result of information flow control based on such workflow models orproject data, the association of a plurality of sections or employeesperforming work by a cooperative effort is facilitated.

Below, typical functions and operations of the solution software suite 4will be concretely described with reference to various GUI windows(shown as examples in FIG. 7 and subsequent figures) that are providedto the user terminals 9 by the solution server 3 (solution softwaresuite 4) via the web server 8. In all of the GUI windows shown asexamples below, underlines character sequences have embedded links toobjects or items that correspond to these character sequences, and thesystem is devised so that when a user operates (e.g., clicks on) thesecharacter sequences, the user can view the corresponding objects oritems that are thus linked.

FIGS. 7 through 23 show examples of various GUI windows that areprovided by the workflow manager (WM) 13. The functions and operationsof the WM 13 will be described below with reference to these GUIwindows.

When a user opens the WM 13, a GUI window such as that shown in FIG. 7(for example) is displayed on the display screen of the user terminal.

The GUI window shown in FIG. 7 is constructed from a plurality ofsub-windows 300, 301, 500 and 501. An object button 302, review button303, workflow button 304, project button 305 and administrator button307 are provided in the upper and lower sub-windows 300 and 301. Theuser can selectively open the abovementioned five types of managers 11through 15 that are contained in the solution software suite 4 bypressing the respective buttons (e.g., by clicking on the buttons with amouse). Furthermore, the user can log out from the solution server 3(solution software suite 4) by pressing the logout button 306 in theupper sub-window 300. The upper and lower sub-windows 300 and 301 aredisplayed in common when any of the managers 11 through 15 is opened.

The two central sub-windows 500 and 501 provide specific GUI to the WM13.

The sub-window 500 on the left side in the center is called a workflowstructure window. Here, tree-form hierarchical logical structures(workflow structures) of workflow models for various business processesthat are currently registered in the data base are graphically displayedusing folder icons that express various data items of work models.Specifically, the workflow models of various business processes createdby the user are managed in the data base by means of the WM 13 usinglogical hierarchical data structures such as those shown in the workflowstructure window 500.

In the example shown in FIG. 7, a folder named “TKIC” is displayedinside the workflow structure window 500. This folder “TKIC” expresses aspecified business category that has the name of “TKIC” (e.g., anindividual organization such as an enterprise group, individualenterprise, working section within an enterprise, factory, supportingfirm or the like, or a category such as year of work, scope of work,object of work or the like; these categories can be freely set inaccordance with the convenience of the enterprise by a specified personauthorized to make such settings, such as a system administrator or thelike). When this folder “TKIC” is opened, process folders thatrespectively express business processes with the names of “design”,“development”, “scope”, “testing” and “training” are displayed beneaththe folder. This means that business processes called “design”,“development”, “scope”, “testing” and “training” are registered underthe business category called “TKIC” (e.g., an enterprise with the nameof “TKIC”).

When the process folders expressing respective business processes areopened, section folders respectively expressing one or a plurality ofsections responsible for the business processes in question aredisplayed beneath the process folders. For example, section foldersrespectively expressing the sections “R & D”, “Finance”, “Hardware” and“Software”, which are responsible for the business process “design”, aredisplayed beneath the process folder for the business process “design”.

Furthermore, as is shown for example in FIG. 8, when the section foldersfor the respective sections are opened, employee folders respectivelyexpressing one or a plurality of employees belonging to these sections(or employees who belong to the sections and have the authorization tohandle the business processes in question) are displayed. For example,employee folders respective expressing the employees “Jack”, “Fred”,“Hemant” and “Yukio” who belong to the section “R & D” (or who belong tothe section “R & D” and have the authorization to handle the businessprocess “design”) are displayed beneath the section folder for thesection “R & D”, which is located beneath the process folder for thebusiness process “design”.

Referring again to FIG. 7, a section button 502 and a shift button 503are provided in the workflow structure window 500. When the sectionbutton 502 is pressed, only section-wise business processes are selectedor displayed with emphasis inside the workflow structure window 500, andwhen the shift button 503 is pressed, only shift-wise business processesare selected or displayed with emphasis inside the workflow structurewindow 500. The example shown in FIG. 7 illustrates a case in which thesection button 502 has been pressed; here, only the section-wisebusiness processes, e.g., “design”, “development” and “scope”, aredisplayed with emphasis. On the other hand, the example shown in FIG. 9illustrates a case in which the shift button 503 has been pressed; here,only the shift-wise business processes, e.g., “testing” and “training”,are displayed with emphasis. Here, the term “section-wise businessprocess” refers to a business process that is performed by one sectionor by the cooperation of a plurality of sections, while the term“shift-wise business process” refers to a business process that isperformed by the alternation of a plurality of shifts. As will bedescribed later, the WM 13 provides different workflow model creationtools to the user terminal when the workflow model of a section-wisebusiness process is created or edited, and when the workflow model of ashift-wise business process is created or edited. Furthermore, when theWM 13 registers a created or edited business process workflow model inthe data base, the WM 13 can register this workflow model in the database after associating information that indicates the type of thebusiness process (section-wise or shift-wise) with the workflow model.Furthermore, the WM 13 can distinguish the types of these businessprocesses from the abovementioned information that is associated withthe workflow models of the various business processes in the data base.

Furthermore, in the environment settings performed by the systemadministrator using the administration manager (AM) 15, an arbitrarysetting can be made as to which of the types of business processes(among section-wise and shift-wise business processes) is madeimpossible to create. In cases where only one type of business process(among section-wise and shift-wise business processes) is set asimpossible to create in these environment settings, the WM 13 candisable the creation function for the type of business process that isset as impossible to create, and disables the abovementioned functionthat alters the processing such as the display and creation of workflowmodels and the like in accordance with the type of business process.

Referring to FIG. 7, the sub-window 501 on the right side in the centeris called the workflow manager (WM) main window; a process list 507which lists all of the business processes that are registered under aselected business category (e.g., “TKIC”) is displayed in this mainwindow. Information for items such as the name of the process (processname), date and time of creation (creation date), revision No. (rev.No.), author (author), one or more business forms that will be used(form), select (select) button and the like is displayed for eachbusiness process in this business process list 507. When the processnames of the respective business processes in the process list 507 areopened (e.g., double-clicked on with the mouse), the WM 13 displays thedetails of the workflow model of the business process in question in themain window 501.

Furthermore, a registration combo box 504, a workflow combo box 505 anda search combo box 506 are provided in the upper part of the WM mainwindow 501. The registration combo box 504 is used to select the type ofitem for which registration is desired in cases where the user desiresto register various types of items relating to business processes. As isshown in FIG. 7, menu items for various item types such as process,section, task, sub-task, shift and the like are provided in a pull-downmenu 504M. The workflow combo box 505 is used to select the type ofworkflow model that the user desires to create or edit in cases wherethe user desires to create or edit a business process workflow model; aconcrete description of this combo box 505 will be given later. Thesearch combo box 506 is used to select the type of item for which asearch is to be made in cases where the user searches for items relatingto business processes.

In cases where the user desired to register a new business process, ordesires to alter or delete a registered business process, the user canopen the pull-down menu 504M of the registration combo box 504, and canselect the “process” menu item from the pull-down menu 504M, as shown inFIG. 7. When this is done, as shown in FIG. 8, the WM 13 displays a newbutton 508, alter button 509, delete button 510, OK button 511 and thelike beneath the process list 507 inside the main window 501. The newbutton 508 is used to register new business processes. The alter button509 and delete button 510 are respectively used to alter and delete oneregistered business process (the business process “training” in theexample shown in FIG. 8) that is selected by the select button withinthe process list 507.

In the main window 501 shown in FIG. 8, when the user presses the newbutton 508, the WM 13 displays new process registration tools in themain window 501 as shown in FIG. 9. These new process registration toolsinclude a process basic information table 512, form selection tools 513and 514, and an OK button 516. The user can enter the process name,revision No. and author name of the new business process in the processbasic information table 512. The form selection tools 513 and 514include display and selection boxes for various types of forms that havebeen registered beforehand by the system administrator using theadministration manager 15; this allows the user to select one or moreforms used in this business process from the forms that have beenregistered beforehand. In the example shown in FIG. 9, two types offorms, i.e., “approval” and “default”, have been selected as the formsused in the new business process “change control” from the three typesof forms “approval”, “default” and “specifications” that have beenregistered beforehand. When the respective form names of the formselection tools 513 and 514 are operated (e.g., double-clicked), the WM13 displays the forms in the main window 501 as shown in FIG. 10. Theexample shown in FIG. 10 shows the form “specifications”; this formincludes various entry boxes 518 through 522 that have been setbeforehand by the system administrator using the administration manager15. When the return button displayed beneath the form in the main window501 shown in FIG. 10 is pressed, the display of the main window 501returns to the new process registration tools shown in FIG. 9.

In the new process registration tools in the main window 501 shown inFIG. 9, specified items are entered in the process basic informationtable 512, and the forms that are to be used are selected using the formselection tools 513 and 514. Then, when the OK button 516 is pressed,the WM 13 registers the process name, revision No., author, types offorms used and the like (relating to the new business process set by thenew process registration tools) in the data base as a part of thehierarchical data structure (already described) of the workflow model ofthis new business process. Then, the WM 13 again displays the processlist 507 in the main window 501 as shown in FIG. 11; in this case,however, a display of the new business process just registered, e.g.,“change control”, is added.

In cases where the user desires to create or edit an arbitrary businessprocess workflow, the user can open the pull-down menu 505M of theworkflow combo box 505, and select the section-wise workflow builder(builder (section-wise) or shift-wise workflow builder (builder(shift-wise)) from this pull-down menu 505M, as shown in FIG. 11.

In cases where the user wishes to create or edit a section-wise businessprocess workflow model, the user can select the section-wise workflowbuilder (builder (section-wise)). When this is done, the WM 13 selectsand displays only section-wise business processes in the process list507, and displays an OK button 524, view button 525, alter button 526,delete button 527, cancel button 528 and the like beneath this processlist 507, as shown in FIG. 12. On the other hand, if the user selectsthe shift-wise workflow builder (builder (shift-wise)), the WM 1 selectsand displays only shift-wise business processes in the process list 507,and displays similar buttons 524 through 528 beneath this process list507, as will be described later with reference to FIG. 17. Here, it hasnot yet been determined whether the type of the new business processjust registered (e.g., “change control”) is section-wise or shift-wise;however, this is displayed in the process list 507 regardless of whetherthe section-wise or shift-wise workflow builder has been selected.

In cases where section-wise workflow builder (builder (section-wise)) isselected as shown in FIG. 12, if the user desires to create a newworkflow model for a certain business process, the user can select thisbusiness process from the process list 107, and can then press the OKbutton 524. Furthermore, in cases where the user desires to alter aworkflow model that has already been created for a certain existingbusiness process, the user can select this business process from theprocess list 507, and can then press the alter button 526.

Here, for example, let us assume that the user has selected the businessprocess “change control” from the process list 507, and has pressed theOK button 524. When this is done, the WM 13 displays the tools used tocreate and edit a section-wise workflow model for the selected businessprocess “change control” in the main window 501 as shown in FIG. 13. Thedisplayed workflow model creation tools include a section combo box 521,a confirm section button 532, a alter button 533, an add button 534, adelete button 535, a conv from button 536, a conv to button 537, anattribute button 538, a converge button 539, a return button 540, aworkflow display area 541 and the like. One example of the procedureused to create a workflow using these tools will be described below.

As is shown in FIG. 13, the user can select the section that is to bethe starting point of this business process “change control”, e.g., “R &D”, using the section combo box 521, and can the press the add button534 and press the confirm section button 532. When this is done, the WM13 displays the icon 542 of the selected section “R & D” in the workflowdisplay area 541, and causes the section “R & D” to be confirmed as thestarting point of this business process “change control”, as shown inFIG. 1.

Subsequently, as is shown in FIG. 15, the user can select the sectionthat is to take over the work from the starting point section “R & D”,e.g. “finance”, using the section combo box 521, and can then press theadd button 534 and press the confirm section button 532. When this isdone, the WM 13 displays the icon 543 of the “finance” section in theworkflow display area 541, and displays an arrow 544 that points towardthe icon 543 of the “finance” section from the icon 542 of the “R & D”section, thus confirming that the “finance” section is the section thatis to take over the work from the “R & D” section. Furthermore, if thereis another separate section that is to take over the work from the “R &D” section, e.g., “hardware”, the user can perform an operation similarto that described above for the “hardware” section as well. When this isdone, the WM 13 displays the icon 545 of the “hardware” section in theworkflow display area 541 in the same manner as that described above forthis “hardware” section as well, and displays an arrow that pointstoward to the icon 545 of the “hardware” section from the icon 542 ofthe “R & D” section, thus confirming the “hardware” section as anothersection that is to take over the work from the “R & D” section.

Subsequently, as is shown in FIG. 16, the user can select a section thatis to take over the work from both the “finance” and “hardware”sections, e.g., “quality test”, using the section combo box 521, and canthen press the add button 534 and press the confirm section button 532.When this is done, the WM 13 displays the icon 547 of the selected“quality test” section in the workflow display area 541 as shown in FIG.16. Furthermore, the user can press the conv from button 536 afterrespectively clicking on the icons 543 and 545 of the “finance” and“hardware” sections, and can further press the conv to button 537 afterclicking on the icon 547 of the “quality test” section. When this isdone, the WM 13 displays arrows 548 and 549 that respectively pointtoward the icon 547 of the “quality test” section from the icons 543 and545 of the “finance” and “hardware” sections, thus confirming the“quality test” section as the section that is to take over the work fromboth the “finance” and “hardware” sections, as shown in FIG. 16.

In this way, a section-wise workflow model is created, and this model isgraphically displayed in the form of a flow chart in the workflowdisplay area 541. For example, in the flow chart of the workflow modeldisplayed in the workflow display area 541 in FIG. 16, the section icons542, 543, 545 and 547 express the sections that are to perform thisbusiness process “change control”, and the arrow 544, 546, 548 and 549express the flow of work and documents among these sections.

In FIG. 16, when the user presses the return button 540, the WM 13confirms the workflow model of this business process “change control” asa model according to the flow chart shown in FIG. 16, and registers thisworkflow model in the data base; furthermore (although this is not shownin the figures), the WM 13 adds the folder icon of this “change control”business process to the workflow structure window 500. When this “changecontrol” business process is actually performed within a certainproject, the project manager (PM) 14 controls the order in which tasksare performed among the sections using the order of sections accordingto the flow chart shown in FIG. 16, as has already been described withreference to FIG. 6.

Referring again to FIG. 11, in cases where the user desires to create oredit a shift-wise business process workflow model, the user can selectthe shift-wise workflow builder (builder (shift-wise)) in the workflowcombo box 505. When this is done, the WM 13 selects and displays onlyshift-wise business processes in the process list 507, and displays anOK button 524, view button 525, alter button 526, delete button 527,cancel button 528 and the like beneath the process list 527, as shown inFIG. 17. In cases where the user desires to create a new workflow modelfor a certain business process, the user can press the OK button 524after selecting this business process from the process list 507.Furthermore, in cases where the user desires to alter a workflow modelthat has already been created for a certain business process, the usercan press the alter button 526 after selecting this business processfrom the process list 507.

Here, let us assume for example that the user has selected the“training” business process from the process list 507, and has pressedthe alter button 526. When this is done, as shown in FIG. 8, the WM 13displays the tools that are used to alter and edit a shift-wise workflowmodel for the selected business process “training” in the main window501. A shift sequence table 550, a make flow button 551 and the like areincluded in the displayed workflow model creation tools. A workflow thathas already been created for the “training” business process isdisplayed in the shift sequence table 550. This workflow defines thesequence in which a plurality of pre-registered shifts, e.g.,“afternoon”, “morning” and “night”, are to be alternated. Using theshift sequence table 550, the user can freely alter the sequence of the“afternoon”, “morning” and “night” shifts. Furthermore, when the useroperates (e.g., double-clicks on) the arbitrary shift names “afternoon”,“morning” and “night” in the shift sequence table 550, the WM 13displays lists of the employees belonging to these shifts in the mainwindow 501 (although this is not shown in the figures).

After altering the workflow in the shift sequence table 550, the usercan press the make flow button 551. When this is done, the WM 13displays a shift flow table 552 which expresses the workflow followingmodification in the main window 501 as shown in FIG. 19. When the userpresses the submit button 553, the WM 13 confirms the workflow model ofthe “training” business process as the model shown in the shift flowtable 552, and registers this workflow model in the data base.

Referring again to FIG. 7, when the user selects a task as an item to beregistered in the registration combo box 504, the WM 14 displays a tasklist 554 that lists the registered tasks in the main window 501, anddisplays a new button 555, alter button 956, delete button 557, OKbutton 558 and the like beneath this task list 554, as shown in FIG. 20.In cases where the user desires to create and register a new task, theuser can press the new button 555. When this is done, the WM 13 displaysnew task registration tools in the main window 501 as shown in FIG. 21.A basic information table 560, an OK button 564 and the like areincluded in the new task registration tools that are displayed. The usercan enter the task name, revision No., author name, deliverable time,duration, unit and the like of the new task in the basic informationtable. Furthermore, when the user presses the OK button 564, the WM 13creates a new task which has the basis information entered in the basicinformation table 560, and registers this new task in the data base.

Referring again to FIG. 7, when the user selects a sub-task as an itemthat is to be registered in the registration combo box 504, the WM 14displays a task registration GUI comprising two sub-windows 570 and 571in the main window 501 as shown in FIG. 22. The left-side sub-window 570of this GUI is called the “task structure window”; a tree-formhierarchical logical data structure constructed from the data for all ofthe tasks registered in the data base and the sub-tasks included in eachof these tasks is graphically illustrated in this sub-window usingfolder icons that respectively express the tasks and sub-tasks.Specifically, the data of the tasks and sub-tasks that are registered inthe data base are in a hierarchical structure of the type shown in thefigures, a hierarchical data structure of any number of strata can beconstructed, so that not only are one or more sub-tasks included in agiven task, but one or more even more detailed sub-tasks are included ina given sub-task.

In cases where the user desires to register a new sub-task under acertain registered task or sub-task, the user selects the desiredregistered task or sub-task in the task structure window 571, entersbasic attribute information such as the name of the new sub-task(sub-task name), revision No. (Rev. No.), name of the author (authorname), planned starting time (expected start time), required number ofdays (duration) and the like in the sub-task information table 572displayed in the right-side sub-window 571, and further enters the namesof one or more types of document templates that will be used in thecreation of one or more types of documents as deliverables resultingfrom the performance of the new task in the document template table 574displayed in the right-side sub-window 571. When the document templatenames are entered, the user can press the search template button 573;when this is done, the WM 13 displays a document template list 581 thatlists the names of all of the registered document templates in thesub-window 5721 as shown in FIG. 23. When the user selects one or morearbitrary document templates from the document template list 581, andpresses the submit button 582, the display on the screen again returnsto the display shown in FIG. 22, and the names of the one or moredocument templates that have now been selected are entered in thedocument template table 574. Furthermore, when the user operates (e.g.,double-clicks on) arbitrary document template icons displayed in theview column in the document template table 574 shown in FIG. 22 or thedocument template list 581 shown in FIG. 23, the WM 14 opens thedocument templates corresponding to these icons, and displays thesedocument templates on the screen. In FIG. 22, when the user presses theOK button 575 in the sub-window 571, the WM 14 creates new sub-task datawhich has the information entered in the task information table 572 anddocument template table 574 in the sub-window 571, and registers thisnew sub-task data in the data base as the data of one sub-task includedin the registered task or sub-task selected in the task structure window571. Thus, the user can register various sub-tasks in the form oftree-form hierarchical structures under arbitrary tasks.

Referring again to FIG. 7, when the user selects a section or shift asan item that is to be registered in the registration combo box 504, theWM 13 displays a list of registered sections or shifts in the mainwindow 501, and (as in the case of the task shown in FIG. 20) displays anew button, alter button, delete button, OK button and the like beneaththis list (although this is not shown in the figures). If the userpresses the new button, the WM 13 displays tools used to create a newsection or new shift in the main window 501 (although this is not shownin the figures); then, the user can create a new sub-task, section orshift using these tools. The WM 13 registers the new sub-task, sectionor shift that has thus been created in the data base.

FIGS. 24 through 39 and FIGS. 46 through 54 shows various GUI windowsthat are provided by the PM 14. FIGS. 40 through 44 show example ofseveral GUI windows that are provided by the object manager (OM) 11 inassociation with the function of the PM 14. FIG. 45 is a flow chartshowing the procedures for the PM 14 to prepare a task list. Below, thefunctions and operations of the PM 14 and the associated functions andoperations of the OM 11 will be described with reference to thesefigures.

When the user opens the PM 14, a GUI window such as that shown in FIG.24 (for example) is displayed on the display screen of the userterminal.

As has already been described, the upper and lower sub-windows 300 and301 of the GUI window shown in FIG. 24 are common to all of themanagers. The two sub-windows 600 and 601 in the center provide a GUIthat is peculiar to the PM 14.

The sub-window 600 on the left side in the center is called a “projectstructure window”. A tree-form hierarchical logical structure (projectstructure) of various types of project data currently registered in thedata base is graphically displayed in this sub-window 600 using foldericons expressing various data items that are contained in this projectdata. Specifically, various types of project data created by the userare managed in the data base by the PM 14 using a logical hierarchicaldata structure of the type shown in the project structure window 600.

In the example shown in FIG. 24, a folder “TKIC” expressing a specifiedbusiness category that has the name of “TKIC” (e.g., an individualorganization such as an enterprise group, individual enterprise, workingsection within an enterprise, factory, supporting firm or the like, or acategory such as year of work, scope of work, object of work or thelike) is provided inside the project structure window 600. When thisfolder “TKIC” is opened, project folders respectively expressing twoprojects that have the names of “EDMS” and “ABMS” are displayed underthis folder. This means that projects called “EDMS” and “ABMS” areregistered under a business category called “TKIC” (e.g., an enterprisewith the name of “TKIC”).

When the project folders expressing the respective projects are opened,process folders respectively expressing one or a plurality of businessprocesses constituting these projects are displayed under these projectfolders. For example, process folders respectively expressing the twobusiness processes “development” and “design” contained in the project“EDMS” are displayed under the project folder of the project “EDMS”.When the respective business process folders are opened, section foldersrespectively expressing one or a plurality of sections that will beresponsible for these business processes are displayed under the processfolders. For example, section folders respective expressing the sections“R & D”, “finance”, “hardware” and “software” that will be responsiblefor the business process “design” are displayed under the process folderfor the business process “design”. Furthermore, when the respectivesection folders are opened, task folders respectively expressing one ora plurality of tasks that are assigned to the sections with respect tothe business processes of the project are displayed under these sectionfolders. For example, a task folder expressing the task “modular design”which is assigned to the “software” section with respect to the process“design” of the project “EDMS” is displayed under the section “software”for the process “design” of the project “EDMS”. When the task foldersfor the respective tasks are opened, for example, sub-task foldersrespectively expressing one or a plurality of sub-tasks contained in thetasks are displayed (although this is not shown in the figures).

Project data having such a hierarchical logical structure displayed inthe project structure window 600 is created and registered in the database by the user using the functions of the PM 14 which will bedescribed below.

In FIG. 24, the sub-window 601 on the right side in the center is calledthe “project manager (PM) main window”; a project list 607 which listsall of the projects registered under the selected business category(e.g., “TKIC”) is displayed in this sub-window. Information items suchas the name of the project (project name), date and time of creation(creation date), revision No. (rev. No.), project manager (manager),select button an the like are displayed in this project list 607 foreach project.

A registration combo box 602, assign combo box 603, status combo box 604and search combo box 505 are provided in the upper part of the PM mainwindow 601. The registration combo box 602 is used to select the typesof items to be registered in cases where the user desires to registervarious types of items relating to the project. As is shown in FIG. 24,menu items for various types of items such as project, task, sub-task,phase, role and the like are provided in the pull-down menu 602M of thisregistration combo box 602. The assign combo box 603 is used to selectitems that are to be set in cases where various types of workassignments or work schedules relating to the project are set. Thiscombo box 603 will be concretely described later. The status combo box604 is used to select items to which reference is to be made in caseswhere reference is made to various types of status relating to theproject. This combo box 604 will be concretely described later. Thesearch combo box 605 is used to select types of items for which a searchis to be made in cases where a search is made for various types of itemsrelating to the project.

In cases where the user desires to register a new project, or in caseswhere the user desires to alter or delete a registered project, the usercan open the pull-down menu 602M of the registration combo box 602, andcan select the menu item “project” from the pull-down menu 602, as shownin FIG. 24. When this is done, the PM 14 displays a new button 608,alter button 609, delete button 610, OK button 611 and the like beneaththe project list 607 inside the main window 601 as shown in FIG. 25. Thenew button 608 is used to register new projects. The alter button 609and delete button 610 are respectively used to alter and delete oneregistered project (the project “EDMS” in the example shown in FIG. 25)that is selected by the select button within the project list 607.

In the main window 601 shown in FIG. 25, when the user presses the newbutton 608, the PM 14 displays new project registration tools in themain window 601 as shown in FIG. 26. These new project registrationtools include a project basic information table 612, a list of allprocesses 613, a process select button 614, a list of selected processes615, an OK button 616 and the like. The user can enter the project name,revision No. and project manager name of the new business project in theproject basic information table 612. The names of all of the businessprocesses that have already been registered in the data base by theworkflow manager (WM) 13 are displayed in the list of all processes 613.When the user selects an arbitrary business process from the list of allprocesses 613 (e.g., by clicking with the mouse) and presses the processselect button 614, the PM 14 takes the selected business process as abusiness process that is included in this project, and adds the name ofthis business process to the selected process list 615. The exampleshown in FIG. 26 shows how a new project “PROJ1” is created. Here, twobusiness processes “testing” and “training” are selected as businessprocesses of this project “PROJ1”.

In the new project registration tools displayed in the main window 601shown in FIG. 26, when the OK button 616 is pressed after required itemshave been entered in the project basic information table 612 and one ormore business processes have been entered in the selected process list615, the PM 14 registers the project name, revision No., project managername, names of business processes contained in the project and the likerelating to the new project set by the new project registration tools inthe data base as a part of the hierarchical data structure (alreadydescribed) of the project data of this new project. Furthermore, the PM14 again displays the project list 607 in the main window 601 as shownin FIG. 24; in this case, however, a display of the new project that hasjust been registered, e.g., “PROJ1”, is added to the process list 607(although this is not indicated in the example shown in FIG. 24).

Referring again to FIG. 24, in cases where the user desires to registera new task, or in cases where the user desires to alter or delete aregistered task, the user can select the menu item “task” from thepull-down menu 602 of the registration combo box 602. When this is done,the PM 14 displays a GUI similar to the task registration GUI of the WM13 already described with reference to FIGS. 20 and 21 in the PM mainwindow 601, thus allowing the user to register new tasks in the database by a procedure similar to that of task registration using the WM13. Furthermore, in cases where the user wishes to register a newsub-task, or in cases where the user wishes to alter or delete aregistered sub-task, the user can select the menu item “sub-task” fromthe pull-down menu 602 of the registration combo box 602. When this isdone, the PM 14 displays a GUI similar to the sub-task registration GUIof the WM 13 already described with reference to FIGS. 22 and 23 in thePM main window 601, thus allowing the user to register new tasks in thedata base by a procedure similar to that of sub-task registration usingthe WM 13.

Furthermore, in cases where the user wishes to register a new work phase(phase) (here, the term “work phase” refers to several phases obtainedby splitting the flow of work for management purposes in cases where(for example) the work involved in a single business process isperformed by a single section), or in cases where the user wishes toalter or delete a registered work phase, the user can select the “workphase” (“phase”) menu item from the pull-down menu 602 of theregistration combo box 602. When this is done, the PM 14 displays aphase list 617 which lists the work phases that have been registered inthe data base in the main window 501, and displays a new button 618,alter button 618, delete button 620, OK button 621 and the like beneaththis phase list 617, as shown in FIG. 27. In the example shown in FIG.27, three registered business phases, i.e., “intrim (initial stream)”,“midstream” and “final”, are listed in the phase list 617. In caseswhere the user desires to create and register a new work phase, the usercan press the new button 618. When this is done, as shown in FIG. 28,the PM 14 displays new task registration tools in the main window 501. Abasic information table 622, an OK button 623 and the like are includedin the new task registration tools that are displayed. When the userenters the phase name, revision No., author name and the like in thebasic information table 622 and then presses the OK button 623, the PM14 creates a new work phase which has the basic information entered inthe basic information table 622, and registers this new work phase inthe data base.

Referring again to FIG. 24, when the user opens the project names of therespective projects in the project list 607 displayed in the main window601 (e.g., when the user double-clicks on the project names with themouse), the PM 144 reads out the project data of these projects from thedata base, and displays detailed information concerning the projects inthe main window 601 as shown for example in FIG. 29. In addition to atable 624 which shows basic information for the project in question,this detailed information includes a process list 625 which lists one ora plurality of business processes constituting the project. When theuser selects a process name in this process list (e.g., when the userdouble-clicks on such a process name with the mouse), the PM 14 readsout the data of the workflow model of this business process from thedata base, and displays the details of this workflow model in the mainwindow 601. When the return button 626 is pressed, the PM 14 returns thedisplay in the main window 601 to the initial display shown in FIG. 24.

Next, reference will be made to FIG. 30. In cases where the user desiresto assign tasks or set time schedules with respect to an arbitraryproject among the registered projects, the user can open the pull-downmenu 603M of the assign combo box 603, and select the item that is to beset from this pull-down menu 603M, as shown in FIG. 30. Menu items suchas task—assignment of work phases according to section (task (sectionphase), employee—assignment of roles according to section (employee(section role)), employee—assignment of tasks according to section(employee (section task)), employee—assignment of shifts (employee(shift), section—assignment of tasks (task assign) and the like areprovided in this pull-down menu 603M.

In cases where the user, with respect to an arbitrary project, desiresto assign new tasks for each work phase to one or a plurality ofsections that are responsible for this project, or in cases where theuser desires to alter a task assignment that has already been set, asshown in FIG. 30, the user can select “task—assignment of work phasesaccording to section” (“task (section phase)”) from the pull-down menu603M of the assign combo box 603. When this is done, the PM 14 displaysan OK button 630, a view button 631, a alter button 632, a delete button633, a cancel button 634 and the like beneath the project list 607 asshown in FIG. 31. After selecting the desired project from the projectlist 607, the user can press the OK button 630 if he desires to set anew task assignment for the project, or can press the alter button 632if he desires to alter a set task assignment.

Where, let us assume for example that the user has selected the project“EDMS” from the process list 507, and has pressed the OK button 630.When this is done, as shown in FIG. 32, the PM 14 displays the GUI ofthe section phase manager, which is a tool that is used to assign tasksfor each work phase to the sections that are responsible for the project“EDMS”, in the main window 601. The section phase manager grasps all ofthe business processes (e.g., “development” and “design”) contained inthe project “EDMS” on the basis of the project data for the project“EDMS” in the data base, grasps all of the sections that are responsiblefor the respective business processes (e.g., the four sections “R & D”,“finance”, “hardware” and “software” in the case of the business process“development”) on the basis of the workflow model data for thesebusiness processes in the data base, grasps all of the registered workphases (e.g., the three work phases “interim”, “midstream” and “final”)on the basis of the work phase data in the data base, grasps all of theemployees belonging to the respective sections on the basis of theemployee data for each section in the data base, and grasps all of thetasks assigned to the respective sections (e.g., the two tasks “needanalysis” and “develop specifications” for the section “R & D”) on thebasis of the task data for each section in the data base (this will bedescribed later with reference to FIGS. 35 and 36). Then, on the basisof the abovementioned grasped information, the section phase managerdisplays task—section work phase assignment tables 637 and 638respectively corresponding to each of the business processes“development” and “design” contained in the project “EDMS” in the mainwindow 601 as shown in FIG. 32. In the example shown in FIG. 32, thetask—section work phase assignment table 637 for the first businessprocess “development” is completely displayed in the main window 601,but the task—section work phase assignment table 638 for the secondbusiness process “design” is only partially displayed in the main window601. However, the second task—section work phase assignment table 638can be completely displayed by scrolling the main window 601 using thescroll bar 639 or the like.

For example, the task—section work phase assignment tables 637 and 638for the respective business processes are constructed so that tasks canbe assigned for individual work phases to all of the sectionsresponsible for the business processes by a method such as switchingradio buttons for the respective tasks ON or the like. Furthermore, inthe task—section work phase assignment tables 637 and 638 for therespective business processes, required work amounts (units) can be setfor the tasks assigned to the respective sections for each work phase.Furthermore, the person responsible for the business process in question(among the employees belonging to the section) can be set for eachsection using an “in-charge” column combo box or the like. For example,in the task—section work phase assignment table 637 for the businessprocess “development” shown in the figures, the task “need analysis” isassigned to the section “R & D” in the work phase “interim”, and thetask “develop specifications” is assigned to the same section in thework phase “midstream”. Furthermore, an amount of work equal to 1 unitis set for the task “need analysis”, and an amount of work equal to 3units is set for the task “develop specifications”. Moreover, “FredTanaka” is selected as the person responsible for the business process“development” in the section “R & D”. Furthermore, in the task—sectionwork phase assignment tables 637 and 638, if the user presses (e.g.,clicks on) the name of an arbitrary task, the PM 14 grasps the tree-formhierarchical structure of the task in question that is registered in thedata base, and all of the sub-tasks that are positioned beneath thistask, an displays this hierarchical structure on the screen. As aresult, the user can easily ascertain what kinds of sub-tasks areincluded in each task.

When the user presses the “OK” button (not shown in FIG. 32) that ispositioned beneath the task—section work phase assignment tables 637 and638 on the GUI of the section phase manager shown in FIG. 32 aftermaking the necessary task assignments, setting of work amounts, settingof persons in charge and the like in these tables 637 and 638, the PM 14registers such task assignments, setting of work amounts and setting ofpersons in charge in the data base as a part of the project data of theselected project. When a certain task is thus assigned to a certain workphase in a certain section, all of the sub-tasks contained in thisassigned task are also inevitably assigned to the work phase in questionof the section in question as a result of the hierarchical logicalstructure among tasks and sub-tasks shown for example in the taskstructure window 571 in FIG. 22.

Referring again to FIG. 30, in cases where the user, with respect to anarbitrary project, desires to assign new roles to the employees of oneor a plurality of sections that will be responsible for this project, orin cases where the user desires to alter role assignments that havealready been set, the user can select “employee—section role assignment”(“employee (section role)”) from the pull-down menu 603M of the assigncombo box 603. When this is done, the PM 14 displays a GUI screen thatis substantially similar to that shown in FIG. 31 (already described);accordingly, after selecting a desired project from the project list 607on this GUI screen, the user can press the OK button 630 if he desiresto set a new role assignment for the project, or can press the alterbutton 632 if he desires to alter a role assignment that has alreadybeen set.

Here, for example, let us assume that the user has selected the project“EDMS” from the process list 507, and has pressed the OK button 630.When this is done, the PM 14 displays the GUI of a section role manager,which is a tool that is used to assign one or a plurality ofpre-registered roles to employees of the section that is to beresponsible for the project “EDMS”, in the main window 601 as shown inFIG. 33. The section role manager grasps all of the business processescontained in the project “EDMS” (e.g., “development” and “design”) onthe basis of the project data for the project “EDMS” in the data base,grasps all of the sections that are responsible for the respectivebusiness processes (e.g., the four sections “R & D”, “finance”,“hardware” and “software” in the case of the business process“development”) on the basis of workflow model data for these businessprocesses in the data base, grasps all of the registered roles (e.g.,the four roles “analyst”, “financial controller”, “designer” and “systemengineer”) on the basis of the role data in the data base, and graspsall of the employees belonging to the respective sections on the basisof the employee data for each section in the data base. Furthermore, onthe basis of the abovementioned grasped information, the section rolemanager displays employee—section role assignment tables 641 and 642respectively corresponding to the business processes “development” and“design” contained in the project “EDMS” in the main window 601 as shownin FIG. 33. Even in cases where all of the employee—section roleassignment tables 641 and 642 cannot be simultaneously displayed in themain window 601 (as in the example shown in the figures), the desiredemployee—section role assignment tables can be displayed by scrollingthe main window 601 using the scroll bar 639 or the like.

In the employee—section roll assignment tables 641 and 642 for therespective business processes, combo boxes which have pull-down menuslisting (for example) the names of all of the employees in the sectionare provided in the cells for each role of each section. Any of theemployees in each section can be assigned to the respective roles of therespective sections using the respective combo boxes. When the userpresses the “OK” button (not shown in FIG. 33) disposed beneath theemployee—section role assignment tables 641 and 642 on the GUI of thesection role manager shown in FIG. 33 after assigning the employees thatare to perform the respective roles in these tables 641 and 642, the PM14 registers these role assignments in the data base as a part of theproject data of the selected project.

Referring again to FIG. 30, in cases where the user, with respect to anarbitrary project, desires to assign new tasks to the employees of oneor a plurality of sections that are to be responsible for this project,or in cases where the user desires to alter task assignments that havealready been set, the user can select “employee—section task assignment”(“employee (section task)”) from the pull-down menu 603M of the assigncombo box 603. When this is done, the PM 14 displays a GUI screen whichis substantially similar to that shown in FIG. 31 (described already);accordingly, after selecting the desired project from the project list607 sown on this GUI screen, the user can press the OK button 630 if hedesires to set a new employee—task assignment for this project, or canpress the alter button 632 if he desires to alter an employee—taskassignment that has already been set.

Here, for example, let us assume that the user has selected a projectfrom the process list 507, and has pressed the OK button. When this isdone, the PM 14 displays the GUI of a section task manager, which is atool that is used to assign one or a plurality of tasks that havealready been assigned to the section that is responsible for the project“EDMS” (tasks that have been assigned using the GLI shown in FIG. 32) toemployees of this section, in the main window 601 as shown in FIG. 34.The section task manager grasps all of the business processes containedin the project “EDMS” (e.g., “development” and “design”), the sectionsthat are respectively responsible for these business processes (e.g.,the four sections “R & D”, “finance”, “hardware” and “software” in thecase of the business process “development”), and the tasks that arerespectively assigned to these sections (e.g., the two tasks “needanalysis” and “develop specifications” in the case of the section “R &D” for the business process “development”), on the basis of the projectdata for the project “EDMS” in the data base, and further grasps all ofthe employees belonging to the respective sections on the basis of theemployee data for each section in the data base. Furthermore, on thebasis of the abovementioned grasped information, the section taskmanager displays employee—section task assignment tables 643 and 644respectively corresponding to business processes “development” and“design” contained in the project “EDMS” in the main window 601 as shownin FIG. 34. Even in cases where all of the employee—section taskassignment tables 643 and 644 cannot be simultaneously displayed in themain window 601 (as in the example shown in the figures), the desiredemployee—section task assignment tables can be displayed by scrollingthe main window 601 using the scroll bar 639 or the like.

In the employee—section task assignment tables 643 and 644 for therespective business processes, a combo box which has a pull-down menu inwhich {for example) the names of all of the employees of the section inquestion are listed is provided in the employee cell in the row of eachtask of each section, and any of the employees of this section can beassigned as the person responsible for this task using this employeecomb box. Furthermore, a combo box which has a pull-down menu in which(for example) the names of all of the employees of the section inquestion are listed is provided in the reviewer cell in the row of eachtask, an any of the employees of this section can be assigned as thereviewer of the results of the task performed by the person responsiblefor the task using this employee combo box. Furthermore, the expectedstart time and expected end time of the task in question can be enteredin the expected start time and expected end time cells in the row ofeach task. Furthermore, assignments or settings in the employee—sectiontask assignment tables 643 and 644 can also be left as “open”. When the“OK” button (not shown in FIG. 34) disposed beneath the employee—sectiontask assignment tables 643 and 644 is pressed, the PM 14 registers theassignments and settings in the employee—section task assignment tables643 and 644 in the data base as a part of the project data for theselected project.

Referring again to FIG. 30, in cases where the user desires to assign ingeneral, to an arbitrary section, one or a plurality of tasks that areto be performed by this section, or in cases where the use desires toalter a task that has already been assigned in general, the user canselect “section—task assignment” (“task assign”) from the pull-down menu603M of the assign combo box 603. When this is done, the PM 14 displaysa section list 645 that lists all of the sections registered in the database, and displays an OK button 646, view button 647, alter button 648,delete button 649, cancel button 650 and the like beneath this sectionlist 645, as shown in FIG. 35. After selecting the desired section fromthe section list 645, the user can press the OK button 646 if he desiresto assign a new task to this section, or can press the alter button 648if he desires to alter a task that has already been assigned.

Here, let us assume for example that the user has selected the section“R & D” from the section list 645, and has pressed the OK button 646.When this is done, the PM 14 displays the GUI of a task assign manager,which is a tool that is used to assign tasks in general to the section“R & D”, in the main window 601 as shown in FIG. 36. A section basicinformation table 651, a task list 652, an assign button 653, anassigned task list 654, an OK button 655 and the like are displayed inthe GUI of the task assign manager. Basic information concerning theselected section “R & D” is displayed in the section basic informationtable 651. The names of all of the tasks registered in the data base arelisted in the task list 652. The names of all of the tasks assigned tothe selected section “R & D” are listed in the assigned task list 654.When the user selects an arbitrary task from the task list 652 andpresses the assign button 653, the PM 14 adds the name of the selectedtask to the assigned task list 654. When the user presses the “OK”button 655, the PM assigns the tasks listed in the assigned task list tothe selected section, and registers assigned task data that indicatesthese assigned tasks in the data base. The assigned task data (for eachsection) thus registered is displayed in the rows corresponding to therespective sections in the task—section work phase assignment tables 637and 638 in the GUI of the section phase manager shown for example inFIG. 32 (already described).

Referring again to FIG. 30, in cases where the user desires to assign anarbitrary shift to employees, or in cases where the user desires toalter a shift that has already been assigned, the user can select“employee—shift assignment” (“employee (shift)”) from the pull-down menu603M of the assign combo box 603. When this is done, the PM 14 displaysthe date selection GUI of a shift manager, which is a tool that is usedto assign shifts to employees, in the main window 601 as shown in FIG.37. A calendar table 656 for a selected month, a previous-month button657, a next-month button 658, an OK button 659 and the like aredisplayed in this date selection GUI. When the user operates theprevious-month button 657 or next-month button 658 as necessary so thatthe calendar table 656 for the desired month is displayed, and thenpresses the OK button 659, and then selects the desired data in thiscalendar table 656 and presses the OK button 659, the PM 14 displays aGUI that is used for employee—shift assignment on the selected date ofthe shift manager in the main window 601 as shown in FIG. 38. Anemployee—shift table 660, a submit button 661 and the like are displayedin this GUI used for shift assignment. All of the shift employeesregistered in the data base are listed in the employee—shift table 660,and the system is arranged so that any shift selected from a pluralityof shifts registered in the data base (e.g., “morning”, “afternoon” and“night” registered using the workflow manager 13) can be assigned to therespective employees using (for example) a combo box. When the userpresses the submit button 661 after assigning desired shifts to desiredemployees using the employee—shift table 660, the PM 14 displays a GUIused for shift assignment confirmation (as shown in FIG. 39) in the mainwindow 601. A shift assignment table 663 indicating the shiftassignments determined by the employee—shift table 660 shown in FIG. 38,a submit button 664 and the like are provided in the GUI used for shiftassignment confirmation. When the user presses the submit button 664,the PM 14 registers shift assignment data expressing the shiftassignments in the data base.

As a result of the functions of the PM 14 described above, project datain which workflow model data for one or a plurality of businessprocesses contained in the process (e.g., 184, 197 and the like in FIG.6), form definition data containing one or a plurality of formsrespectively used in these business processes (e.g., 185 in FIG. 6),task assignment data (for each work phase) for one or a plurality ofsections that are respectively responsible for these business processes(e.g., 192 in FIG. 6), setting data for the expected start and end timesof the work for these sections (e.g., 191 in FIG. 6), role assignmentdata for the employees of these sections (e.g., 193 in FIG. 6) and thelike are associated can be registered in the data base for each project,as in the case of the project data 183 for the project “PROJ1” shown asan example in FIG. 6.

As was described with reference to FIG. 6, the PM 14 creates task lists181 and 182 (shown for example in FIG. 6) which indicate tasks that areto be performed (or that cannot be performed) by the respective sectionsor employees in order to perform the projects in question on the basisof project data for all of the projects registered in the data base.These task lists 181 and 182 are provided to the user terminals of therespective sections or employees by the object manager (OM) 11. FIGS. 40through 44 show examples of several GUI screens that are provided to theuser terminals of the respective sections or employees by the OM 11 onthe basis of the task lists.

FIG. 40 shows one example of the GUI window of the OM 11 that isdisplayed when the user (employee) opens the OM 11.

The sub-windows that are peculiar to the OM 11 in this window are thetwo sub-windows 100 and 101 in the center. The sub-window 100 on theleft side in the center is called a “folder browser window”. A folder“TKIC” which expresses a specified business category (e.g., “TKIC”) isdisplayed in this window, and various hierarchically associated folderswhich are used to manage various objects (documents) registered in thedata base in connection with this business category are displayed underthis folder “TKIC”. The respective folders are displayed by icons whichhave configurations that make it possible to distinguish at a glancewhich folders can be accessed and which folders cannot be accessed bythe employees (e.g., different colors according to this distinction) onthe basis of folder security data for the employees that has been presetusing the administration manager (AM) 15 (e.g., 53 or 54 in FIG. 4).

The sub-window 101 on the right side in the center is called the “objectmanager (OM) main window”. An object list 106 which lists all of theobjects present in the folder that has currently been opened by the userin the folder browser window 100 is displayed in this sub-window 101.Furthermore, a task list button 107, archive room button 108, print roombutton 109, trunk room button 110, work list button 111 and the like arelocated beneath the object list 106. When the user presses the task listbutton 107, the OM 11 displays the GUI shown in FIG. 41 in the mainwindow 101; a task list 112, done task list update (update to done list)button 113, done task list (done list) button 114 and the like aredisplayed in this GUI.

All of the tasks that are currently to be performed or that can beperformed by the user, or that are currently to be managed or that canbe managed by the user, can be listed in the task list 112. For example,the task list 112 is automatically created by the PM 14 on the basis ofthe project data for all of the registered projects, the data for tasksassigned to each section contained in this project data, the currentstate of progress of all of the business projects contained in theproject data, the section to which the user belongs and the like. FIG.45 shows one example of the procedure whereby the PM 14 produces thetask list.

As is shown in FIG. 45, the PM 14 repeats the processing loop of S2 forall of the registered projects. Furthermore, in the processing loop foreach project, the PM 14 repeats the steps from S3 through S5 for all ofthe business processes contained in the project. In step S3, the PM 14grasps the tasks that are respectively assigned to the sectionsresponsible for the business processes (these are the tasks assignedusing the section task manager shown for example in FIG. 32) on thebasis of the project data. In step S4, the PM 14 judges (with respect toeach business process in question) which tasks of which sections can bestarted at the current point in time, this judgement being made on thebasis of the conditions of completion or non-completion of the assignedtasks of each section. For example, the question of whether or not thetasks of a certain section can currently be started or not can be judgedfrom whether or not sections positioned before the section in questionin the order of work in the workflow have completed their assignedtasks. To describe a concrete example, in a case where the workflow ofthe business process is a workflow such as that shown for example in thearea 541 of FIG. 16, if no section has completed it assigned tasks, itcan be judged that the task that can currently be started are only theassigned tasks of the starting section “R & D”. Subsequently, when atleast one of the tasks of the section “R & D” is completed, or when allof the tasks of the section “R & D” are completed, it can be judged thatthe tasks that can currently be started are the assigned tasks of thesecond sections “finance” and “hardware”. Then, when at least one of thetasks of the sections “finance” and “hardware” is completed, or when allof the tasks of the sections “finance” and “hardware” are completed, itcan be judged that the tasks that can currently be started are theassigned tasks of the final section “quality test”. Here, the questionof whether or not the respective tasks have been completed can bejudged, in the GUI as shown in 43 to be described later, for example,according to whether or not a status of “100%” has already been set forall of the deliverables of the sub-tasks contained in the task (thesedeliverables are documents that are created as a result of theperformance of the sub-tasks contained in the task by the personresponsible for the task; these documents can be created using thedocument templates set in the document template table 574 in the GUIshown for example in FIG. 22). Thus, in step S4, the PM 14 extracts thetasks that can currently be started from assigned tasks of each section.In step S5, the OM 11 lists the extracted tasks that can currently bestarted in each section in a task list for each section. The OM 11 canprovide task lists for one or a plurality of sections to which the usersbelong (or which are managed by the users) to the user terminals of theusers.

Reference is again made to FIG. 41. The task name, expected start time,expected end time, status, project, process, section, work phase(phase), role, process manager (in-charge), responsible employee(employee) and the like are displayed in the task list 112 for each ofthe tasks listed in this task list 112. The expected start time andexpected end time can be set in the GUI shown in FIG. 34. The statusindicates whether the task has not yet been started (unmarked), is beingperformed (doing), or has been completed (done). The assigned employeeand role indicate the name and role of the employee responsible for thetask. In cases where data indicating the assignment of the task to anemployee is not contained in the registered project data, nothing isinitially displayed in the assigned employee and role cells. Later,however, when a certain employee starts the task (e.g., when thisemployee presses the OK button 119 in the GUI shown in FIG. 44, whichwill be described next), the OM 11 displays the name and role of thisemployee in the assigned employee and roll cells of the task list 112.

When the user presses the update to done list button 113 beneath thetask list 112, the OM 11 deletes the tasks whose current status is“done” from the task list 112, and transfers these tasks to the donelist (not shown in the figures). When the user pressed the done listbutton 114, the OM 11 shows the done list (not shown in the figures) inthe main window 101.

Furthermore, when the user selects an arbitrary task name from the tasklist 112 by a method such as (for example) double-clicking or the like,the OM 11 displays a GUI such as that shown in FIGS. 42 and 43 (FIGS. 42and 43 show a case in which the same GUI window has been scrolled in thevertical direction) in the main window 101. A task detail table 115 isprovided in this GUI shown in FIGS. 42 and 43, and detailed informationconcerning the selected task is displayed in this table. A taskstructure box 116 and a task status table 117 are displayed beneath thetask detail table 115. A tree structure of the sub-tasks contained inthe selected task is graphically displayed in the task structure box 116using folder icons that respectively express the task and sub-tasks; thesub-tasks displayed here are sub-tasks that have been registered usingthe GUI shown in FIGS. 22 and 23. When the user selects an arbitrarysub-task from the task structure box 116, the OM 11 displays iconsexpressing one or more document templates used to create thedeliverables of the selected sub-task (these are document templates thathave been set in the document template table 574 in the GUI shown forexample in FIG. 22) in the left-end portion of the task status table117, and displays the character sequence “attach” on the right side ofthese icons. When the user selects an arbitrary icon in the task statustable 117 by an operation such as checking or the like, the OM 11 opensthe document template corresponding to the selected icon on the screen;accordingly, the user can create documents as deliverables using thisdocument template, and can store these document files in an arbitrarydirectory. When the user selects the character sequence “attach” insidethe task status table 117 by an operation such as clicking or the like,the OM 11 opens a tool which is used to attach an arbitrary documentfile of this arbitrary directory to the selected task as a deliverable(e.g., a tool which has a function similar to the attachment tool thatis used to select attached documents in a common email program).Accordingly, using this attachment tool, the user can attach documentfiles that were just created and stored using the document template asdeliverables of the selected sub-task. When a deliverable document fileis thus attached, the OM 11 changes the character sequence “attach” thatwas just operated in the task status table 117 to the file name of theattached document file. For instance, in the example shown in FIG. 43,the document file name “spec list” is displayed in the task status table117; this means that a document file with the name of “spec list” hasbeen attached as a deliverable of the selected task. When the userselects an attached document file name in the task status table 117 byan operation such as (for example) clicking or the like, the OM 11 opensthis document file; accordingly, the user can view the contents of thisdocument file. Furthermore, a combo box is provided for each documentconstituting a deliverable at the right end of the task status table117, and the user can enter the status or degree of completion of eachof the documents using these combo boxes. The status and correspondingdegrees of completion that can be selected using these combo boxes(e.g., “start”, “in progress” and “done” as status, and “20%”, “50%” and“100%” or the like as corresponding degrees of completion) can be setbeforehand using the administration manager 15.

A process form table 118 is displayed beneath the task structure box 116and task status table 117, and forms that are used in reports regardingthe selected task (these are forms selected in the GUI shown for examplein FIG. 9 when the business process to which the selected task belongsis registered) are listed in this process form table 118. When the userselects an arbitrary form in the form table 118 by an operation such as(for example) clicking or the like, the OM 11 displays a process worksheet input form such as that shown in FIG. 44 in the main window 101,and the selected form 121 is opened in this input form; accordingly, theuser can input arbitrary report items in this form 121. Furthermore, aform selection combo box 122 which is used to select other report formsused in the selected sub-task, and an attached document table 123 whichlists attached document files as the abovementioned other forms anddeliverables, are displayed beneath this opened form 121. When the userselects an attached document file as another report form or deliverableusing the form selection combo box 122 or attached document table 123,the OM 11 either displays the selected form on the process work sheetinput form in the main window 101, or opens the attached document fileas the selected deliverable on the screen; accordingly, the user canrefer to or edit the displayed form or opened attached document file.When the user presses the submit button 124 displayed at the lower endof the process work sheet input form, the OM 11 returns the display ofthe main window 101 to the GUI shown for example in FIGS. 42 and 43.When the user presses the OK button displayed at the lower en of the GUIin the main window 101 shown for example in FIGS. 42 and 43, the OM 11associates the attached (or edited) report form or attached documentfile (as a deliverable) with the selected sub-task of the selected taskof the selected business process of the selected project, and registersthis form or deliverable in the data base (or updates a form or attacheddocument file that has already been registered in this way). Inaddition, the OM 11 associates the status or degree of completion ofattached document files (as deliverables) that have been entered in thetask status table 117 in the GUI shown in FIGS. 42 and 43 with therespective attached document files, and registers this information inthe data base. Furthermore, in cases where the OM 11 registers one ormore attached document files in the data base as deliverables of acertain task or sub-task, the one or more attached document files can beregistered in the data base as a single object (e.g., with a pluralityof document files being converted into a multi-document object).

Thus, for a certain task belonging to a certain business process of acertain project, when the employee of a certain section that performsthis task temporarily registers a form as a report or an attacheddocument file as a deliverable in the data base, the employee who takesover the following task belonging to the same business process of thesame project can subsequently ascertain the report items or results ofthe previous task from the employee who performed the previous task byselecting the following task from the task list displayed on his ownuser terminal, and opening and viewing the report form or document file(provided as a deliverable), by an operation similar to that describedabove with reference to FIGS. 41 through 44. Furthermore, the employeewho is responsible for the following task can additionally enter his ownreport items in the same report form, or can additionally attachdocument files as the deliverables of his own task. Thus, the flow ofinformation among users or sections that perform projects in cooperationis controlled in accordance with the workflow of the respective businessprocesses contained in the project data, and in accordance with theprogress of the respective business processes.

Here, the description will again return to a description of thefunctions of the PM 14. As is shown in FIG. 46, when the pull-down menu604M of the status combo box 604 in the PM main window 601 is opened,menu items such as task report, executive report, cost and budget,resource, pie chart (cost and time), bar (cost and time), projectschedule, task flow, employee shift and the like are provided in thispull-down menu 604M.

When the user selects “task report” from the pull-down menu 604M of thestatus combo box 604, the PM 14 displays a project table 607 that liststhe currently registered projects in the main window 601, and displays areport OK (OK for reporting) button 665 beneath the project table 607,as shown in FIG. 47. Furthermore, the projects listed in the projecttable 607 are different in the GUI prior to task report selection shownin FIG. 46 and the GUI following task report selection shown in FIG. 47.However, this is merely shown for reasons of convenience in descriptionin the present specification; in actuality, the projects listed in theproject table 607 are the same both before and after the selection ofthe task report.

In FIG. 47, when the user selects a desired project from the projecttable 607 and presses the OK for reporting button 665, the PM 14displays a GUI such as that shown in FIGS. 48 and 49 in the main window601 (FIGS. 48 and 49 show the display obtained when the same GUI isscrolled in the left-right direction). A task reporting table 666 whichexpresses the state of progress and various attributes of all of thetasks and sub-tasks contained in the selected project is displayed inthis GUI. On the basis of the project data of the selected project inthe data base, and the data regarding deliverables of tasks or sub-taskscontained in the selected project associated with this project data, thePM 14 displays the mutual hierarchical relationship among tasks andsub-tasks, the names of objects comprised by combining one or moreattached document files constituting deliverables, the status, the nameof the administrator (task in charge), the name of the reviewer(reviewer), the planned date and time of starting (expected start time),the number of days required (duration days), the planned date and timeof completions (expected end time), the actual date and time of starting(actual start time), the actual date and time of completion (actual endtime), the cost, document templates (templates) and the like in the taskreporting table 666 for all of the tasks and sub-tasks contained in theselected project.

When the user selects the object name of the deliverable of an arbitrarytask or sub-task displayed in the task reporting table 666 by a methodsuch as clicking or the like, the PM 14 displays a list 667 of the namesof the attached document files (i.e., deliverables of the task orsub-task) that constitute the object in the main window 601 as shown inFIG. 50. When the user selects the name of an arbitrary attacheddocument file displayed in the list 667 shown in FIG. 50 by clicking orthe like, the PM 14 opens the attached document file that has this nameand displays this file on the screen.

Referring again to FIGS. 48 and 49, the expected start times andexpected end times of the respective tasks or sub-tasks in the taskreporting table 666 are set beforehand for these tasks or sub-tasksusing the GUI of the section task manager shown for example in FIG. 34.The actual start times and actual end times are the actual start timesand end times of the tasks or sub-tasks that are recognized by the PM14. For example, when the OK button 118 is pressed after some documentfile is attached as a deliverable with respect to such a task orsub-task in the task status table 117 shown for example in FIG. 43 andthe status of this document file is set as “start”, the PM 14 canrecognize that the selected task or sub-task has actually been started,and can set this date and time as the actual start time. Furthermore,for example, when the OK button 118 is pressed after the status of allof document files attached as deliverables with respect to such a taskor sub-task is set as “done” in the task status table 117 shown forexample in FIG. 43, the PM 14 can recognize that the selected task orsub-task has actually been completed, and can set t his data and time asthe actual end time.

The status of the respective tasks or sub-tasks in the task reportingtable 666 shown in FIG. 48 is automatically calculated by the PM 14 onthe basis of the degree of completion of the document files constitutingdeliverables of these tasks or sub-tasks. For example, for a selectedtask or sub-task, the PM 14 can calculate the mean value of the degreesof completion of all of the document files attached as deliverables inthe task status table 117 shown for example in FIG. 43, and can takethis mean value as the status of the selected task or sub-task.Furthermore, the cost of each task or sub-task in the task reportingtable 666 shown in FIG. 49 is automatically calculated by the PM 14 onthe basis of the actual start time and actual end time of the task orsub-task and the hourly compensation rate of the employees responsiblefor this task or sub-task (registered in the data base beforehand usingthe administration manager 15). For example, the PM 14 can estimate theactual working time on the basis of the actual start time and actual endtime of the task or sub-task (e.g., the number of hours obtained bysubtracting the actual start time from the actual end time is multipliedby a specified coefficient and taken as the estimated working time), andthe value obtained by multiplying this estimated working time by thehourly compensation rate of the persons responsible for the task orsub-task can be taken as the cost of the task or sub-task.

Referring again to FIG. 46, when the user selects “executive report”from the pull-down menu 604M of the status combo box 604 in the mainwindow 601, the PM 14 displays a GUI which expresses whether or not theschedule, cost and budget of all of the projects shown in FIG. 51 are asexpected in the main window 601. A combo box 669 is provided in thisGUI, and the user can select either “time” or “cost” using this combobox. When “time” is selected by the combo box 669, the PM 14 displays apie chart and table which indicate that the progress of all of theprojects is on schedule, or how far the progress has deviated form theschedule (e.g., the numbers and proportions of projects respectivelybelonging to the three categories of “on time” (“on target”), “possiblylate” (“at risk”) and “late” (“in trouble”)), in a region 690 within themain window 601. When “cost” is selected by the combo box 669, the PM 14displays a pie chart and table which indicate that the costs of all ofthe projects are as expected, or how fat the costs have deviated fromthe expected costs (e.g., the numbers and proportions of projectsrespectively belonging to the three categories of “as expected or less”(“on target”), “possible exceeding expected cost” (“at risk”) or“exceeding expected cost” (“in trouble”) in a region 690 within the mainwindow 601. Furthermore, a table 691 which expresses the respectivevalues of the degree of completion (percent completed), schedulevariances, cost variance, budget variance, risk factors and the like ofall of the projects is displayed beneath the abovementioned pie chartand table. Furthermore, a “save as spread sheet” button 668 is providedin this GUI, and when the user presses this button 668, the PM 14 storesthe information displayed in this GUI in the form of a tabularcalculation program file.

Referring again to FIG. 46, when the user selects a desired project fromthe project table 607 in the main window 601, and selects “projectschedule” from the pull-down menu 604M of the status combo box 604, thePM 14 displays the GUI of a status manager, which is a tool that managesthe progress of the project shown in FIG. 52, in the main window 601.Process schedule tables 670 and 671 which display the conditions ofprogress of all of the business processes contained in the selectedproject for each business process are displayed in this status managerGUI. The section, task name (task), responsible employee (employee),planned starting date and time (expected start time), planned completiondate and time (expected end time), actual starting date and time (actualstart time), actual completion date and time (actual end time), startingflag (start flag), completion flag (end flag) and the like are displayedfor all of the tasks contained in the business processes in the processschedule tables 670 and 671 for the respective business processes. Here,as was already described above, the expected start time and expected endtime are set beforehand for the tasks in the GUI shown for example inFIG. 34. Furthermore, as was already described above, the actual starttime and actual end time are times recognized by the PM 14 as the actualstart times and end times of the tasks. The start flag and end flag areflags which indicate whether or not the actual start times and actualend times of the tasks are later than the expected start times andexpected end times. For example, in cases where a task has not yet beenstarted even though the expected start time has passed, a special mark(e.g., a red mark) is displayed in the start flag, and in cases wherethe task has not yet been completed even though the expected end timehas passed, a special mark (e.g., a red mark) is displayed in the endflag.

Referring again to FIG. 46, when the user selects a desired project fromthe project table 607, and selects “resource” form the pull-down menu604M of the status combo box 604, the PM 14 displays the GUI of aresource manager, which is a tool that is used to manage human andphysical resources that are invested in the project shown in FIG. 53, inthe main window 601. Process resource tables 672 which display theamounts of resources used in all of the business processes contained inthe selected project for each of these business processes is displayedin the GUI of this resource manager. In the example shown in FIG. 53,only the process resource table of the first business process, e.g.,“development”, among the plurality of business processes contained inthe selected project, e.g., “EDMS”, is displayed. However, the processresource tables of other business processes are displayed if the mainwindow 601 is scrolled by operating the scroll bar 639 or the like. Thesection, role, employee names (employee), standard rate, overtime rate,standard time duration, overtime time duration, labor cost (cost) andthe like for all of the employees invested in the business process inquestion are displayed in the process resource table 672 of eachbusiness process. Furthermore, the material and equipment cost, processlabor cost, process aggregate cost, process effective time, processtime, process efficiency and the like used in this business process arealso automatically calculated and displayed.

Referring again to FIG. 46, when the user selects a desired project fromthe project table 607, and selects “pie chart (cost and time)” from thepull-down menu 604M of the status combo box 604, the PM 14 displays aGUI which is used to compare the cost and time used in the project shownin FIG. 54 among the sections, employees, business processes or tasks inthe main window 601. A combo box 680 which is used to select time orcost, a combo box 682 which is used to select sections, employees,business processes or tasks, a proportion table 684, a pie chart 685 andthe like are displayed in this GUI. Proportional values of respectivesections, respective employees, respective business processes orrespective tasks and a pie chart expressing these proportional values(as the results of a comparison of the time or cost selected by the combbox 680 among the sections, employees, business processes or tasksselected by the combo box 682) are displayed in the proportion table 684and pie chart 685.

Referring again to FIG. 46, when the user selects a desired project fromthe project table 607, and selects “bar graph (cost and time)” from thepull-down menu 604M of the status combo box 604, the PM 14 displays aGUI (not shown in the figures) in which the pie chart in the GUI shownin FIG. 54 is changed to a bar graph in the main window 601.

One concrete example of a method for controlling the flow of informationthat can be employed in one embodiment of the present invention will bedescribed below.

FIG. 55 shows various types of data in the virtual knowledge base 20that is used by the OM 11, RM 12, WM 13, PM 14 and TM 15 in order toperform this method.

As is shown in FIG. 55, numerous objects DOC_aa, DOC_ab, DOC_ac, . . . ,EML_ba, EML_ba, EML_bc, . . . , PRC_ca, PRC_cb, PRC_cc, . . . , TSK_da,TSK_db, TSK_dc, . . . , PRJ_ea, PRJ_eb, PRJ_ec, . . . and DOC_fa,DOC_fb, DOC_fc, . . . are present in the virtual knowledge base 20.Here, the term “object” refers to a logical entity of data that isutilized by the user. These objects include objects of various types.For example, the objects DOC_aa, DOC_ab, DOC_ac, . . . and DOC_fa,DOC_fb, DOC_fc, . . . of one type are document objects, the objectsEML_ba, EML_ba, EML_bc, . . . of another type are email messages, theobjects PRC_ca, PRC_cb, PRC_cc, . . . of still another type are businessprocesses, the objects TSK_da, TSK_db, TSK_dc, . . . of still anothertype are tasks, and the objects PRJ_ea, PRJ_eb, PRJ_ec, . . . of stillanother type are projects. The types of objects described here aremerely examples; other types may also exist. For example, the worklists, task lists and process work sheets that will be described laterare objects of different types from the objects described above.Furthermore, data regarding sections, employees, search queries, menusand the like may also be handled as objects.

As is shown in FIG. 55, a plurality of logical memory regions which areused to store the objects, i.e., the folders DOC FLD_a, DOC_FLD_b, . . ., EML_FOL_a, EML_FOL_b, . . . , PRC_FOL_a, PRC_FOL_b, . . . , TSK_FOL_a,TSK_FOL_b, . . . , PRJ_FOL_a, PRJ_FOL_b, TMP_FOL_a, . . . and DLV_FOL_a,are present in the virtual knowledge base 20. These folders includefolders of various types; objects of specified types are stored in thefolders of these respective types. For example, document objects DOC_aa,DOC_ab, DOC_ac, . . . are stored in the document folders DOC_FLD_a,DOC_FLD_b, . . . , email messages EML_ba, EML_ba, EML_bc, . . . arestored in the email folders EML_FOL_a, EML_FOL_b, . . . , businessprocesses PRC_ca, PRC_cb, PRC_cc, . . . are stored in the processfolders PRC_FOL_a, PRC_FOL_b, . . . , and tasks TSK_da, TSK_db, TSK_dc,. . . are stored in the task folders TSK_FOL_a, TSL_FOL_b, . . . .Furthermore, document objects DOC_fa, DOC_fb, DOC_Fc, . . . used astemplates (pattern document objects used for reference when the usercreates document objects) are stored in the template folders TMP_FOL_a,. . . , and document objects which are user work products (deliverables)are stored in the deliverable folders DLV_FOL_a, . . . . The types offolders, mutual relationships of folders (e.g., hierarchicalrelationships), types of objects stored in the folders and the likeshown in FIG. 5 are merely simple examples used for the sake ofdescription; various other variations can be used in regard to thesepoints.

The abovementioned objects are logical entities; the data constructionsof the respective objects are defined by a plurality of types of objectadministration tables DOC_ADT, ANT_ADT, WKL_ADT, EML_ADT, PRC_ADT, . . .. For example, the document administration table DOC_ADT defines thedocument objects DOC_aa, DOC_ab, DOC_ac, . . . and DOC_fa, DOC_fb,DOC_fc, . . . , and the annotation administration table ANT_ADT definesespecially the annotation (AN) objects (see FIG. 4) among the documentobjects. Further, the work list administration table WKL_ADT defines thework lists (WKL) (see FIG. 4) which are each an aggregate of a pluralityof document objects. Furthermore, the email administration table EML_ADTdefines the email messages EML_ba, EML_ba, EML_bc, . . . , the processadministration table PRC_ADT defines the business processes PRC_ca,PRC_cb, PRC_cc, . . . , and the task administration table TSK_ADTadministers the tasks TSK_da, TSK_db, TSK_dc . . . . Moreover, the tasklist administration table TSK_ADT defines task lists (TKL) (see FIG. 41)which are each an aggregate of a plurality of tasks. Furthermore, theproject administration table PRJ_ADT defines the projects PRJ_ea,PRJ_eb, PRJ_ec, . . . .

The respective managers OM 11, RM 12, WM 13 and PM 14 control theutilization, i.e., operation, of specified types of objects by the user(e.g., reference, creation, editing, deletion, transmission, reception,approval and the like). For example, the OM 11 controls mainly theoperation of the document objects DOC_aa, DOC_ab, DOC_ac, . . . andDOC_fa, DOC_fb, DOC_fc, . . . and work lists (WKL). The RM 12 controlsmainly the operation of the email messages EML_ba, EML_ba, EML_bc, . . .. The WM 13 administers mainly the operation (especially creation) ofthe business processes PRC_ca, PRC_cb, PRC_cc, . . . and tasks TSK_da,TSK_db, TSK_dc . . . . The PM 14 controls mainly the operation of theprojects PRJ_ea, PRJ_eb, PRJ_ec, . . . and the business processes andtasks that constitute these projects. Furthermore, the PM 14 alsocontrols the operation of the templates DOC_fa, DOC_fb, DOC_fc,deliverables and process sheets.

Each of the managers OM 11, RM 12, WM 13 and PM 14 has various functionsthat are used to perform various operations of the objects by the users(e.g., reference, creation, editing, deletion, transmission, reception,approval and the like). For example, as is shown in FIG. 5, the OM 11has the various functions FNC_aa, FUNC_ab, FUNC_ac, . . . that are usedto operate the document objects, and the RM 12 has the various functionsFNC_ba, FUNC_bb, FUNC_bc, . . . that are used to operate the email.Furthermore, the WM 13 has the various functions FNC_ca, FUNC_cb,FUNC_cc, . . . that are used to operate the business processes, and thevarious functions FNC_da, FUNC_db, FUNC_dc, . . . that are used tooperate the tasks. Moreover, the PM 14 has the various functions FNC_ea,FUNC_eb, FUNC_ec, . . . that are used to operate the projects, and thevarious functions FNC_fa, FUNC_fb, FUNC_fc, . . . that are used tooperate the tasks. These functions can be performed by the useroperating the tools corresponding to the respective functions in the GUIrespectively provided by the OM 11, RM 12, WM 13 and PM 14.

Furthermore, as is shown in FIG. 55, various types of control data arepresent in the virtual knowledge base 20 in order to control the variousoperations of the objects by the OM 11, RM 12, WM 13 and PM 14 (i.e., inorder to control the information flow). These types of control datainclude class registration data (CLR), form registration data (FMR),folder registration data (FLR), class security setting data (CLS), formsecurity setting data (FMS), function security setting data (FCS),folder security setting data (FLS) and the like.

The class registration data (CLR) is data that defines one or moreclasses (ordinarily a plurality of classes) that may be possessed by theobjects. Here, the term “class” refers to an object attribute item; suchitems can be freely set by users that have class definitionauthorization. For example, in the case of document objects, a pluralityof classes such as “subject field”, “supervising section name”, “keywords”, “degree of importance”, “degree of confidentiality”, “period ofvalidity” and the like can be set. The form registration data (FMR) isdata that defines one or more forms that can be used in the objects.Here, the term “form” refers to an aggregate of two or more classesselected from the plurality of defined classes. Forms can also be freedefined by users possessing form definition authorization. For example,in cases where classes such as “subject field”, “supervising sectionname”, “key words”, “degree of importance”, “degree of confidentiality”and “period of validity” are defined, a set of the classes “subjectfield”, “supervising section name” and key words can be defined as “formA”, and a set of the classes “subject field”, “degree of importance”,“degree of confidentiality” and “period of validity” can be defined as“form B”. Forms are used for the selection of classes (attribute items)that are to be displayed in cases where the contents of the objects aredisplayed. For example, in a case where the abovementioned “form A” and“form B” are defined, if “form A” is selected, the “subject field” and“supervising section” of the document object are displayed, but the“degree of importance”, “degree of confidentiality” and “period ofvalidity” are not displayed. The folder registration data (FLR) is datathat defines the hierarchical relationships among folders. This folderregistration data (FLR) is automatically created and updated each timethat some folder is created, altered or deleted by the user.

The class security setting data (CLS) is data that defines the accessauthorization of users with respect to classes, i.e., that defines whichusers can access (or not access) which classes. For example, it may bedefined that “user A” can access “class A”, but cannot access “class B”.The form security setting data (FMS) is data that defines the accessauthorization of users with respect to forms, i.e., that defines whichusers can access (or not access) which forms. For example, it may bedefined that “user A” can access “form A”, but cannot access “form B”.The function security setting data (FCS) is data that defines the accessauthorization of users with respect to the functions respectivelypossessed by the OM 11, RM 12, WM 13 and PM 14, i.e., that defines whichusers can access (or not access) which functions. For example, it may bedefined that “user A” can access “function A”, but cannot access“function B”. The folder security setting data (FLS) is data thatdefines the access authorization of users with respect to folders, i.e.,that defines which users can access (or not access) which folders. Forexample, it may be defined that “user A” can access “folder A”, butcannot access “folder B”. Such security setting data (CLS, FMS, FCS,FLS) can be freely define by users possessing security settingauthorization.

Sets of the abovementioned different types of control data exist fordifferent types of objects. For example, document class registrationdata DOC_CLR, document form registration data DOC_FMR, document folderregistration data DOC_FLR, document security setting data DOC_CLS,document form security setting data DOC_FMS, document function securitysetting data DOC_FCS and document folder security setting data DOC_FLSexist for the purpose of controlling the operation of document objects.

Furthermore, email class registration data EML_CLR, email formregistration data EML_FMR, email folder registration data EML_FLR, emailclass security setting data EML_CLS, email form security setting dataEML_FMS, email function security setting data EML_FCS and email foldersecurity setting data EML_FLS exit for the purpose of controlling theoperation of email.

Furthermore, process class registration data PRC_CLR, process formregistration data PRC_FMR, process folder registration data PRCC_FLR,process class security setting data PRC_CLS, process form securitysetting data PRC_FMS, process function security setting data PRC_FCS andprocess folder security setting data PRC_FLS exist for the purpose ofcontrolling the operation of business processes.

Furthermore, task class registration data TSK_CLR, task formregistration data TSK_FMR, task class security setting data TSK_CLS,task form security setting data TSK_FMS and task function securitysetting data TSK_FCS exist for the purpose of controlling the operationof tasks.

Furthermore, project class registration data PRJ_CLR, project formregistration data PRJ_FMR, project folder registration data PRJ_FLR,project class security setting data PRJ_CLS, project form securitysetting data PRJ_FMS, project function security setting data PRJ_FCS andproject folder security setting data PRJ_FLS exist for controlling theoperation of projects.

Furthermore, process work sheet class registration data PWS_CLR, processwork sheet form registration data PWS_FMR, process work sheet classsecurity setting data PWS_CLS, process work sheet form security settingdata PWS_FMS and process work sheet function security setting dataPWS_FCS exist for the purpose of controlling the operation of processwork sheets (reports that are transferred from user to user in theprocess of performing business processes within a certain project).

The OM 11, RM 12, WM 13 and PM 14 can use the abovementioned controldata sets in accordance with the object types respectively handled bythese managers (e.g., can refer to these data sets for new registration,modification and control of object operations). For example, the OM 11uses a set of the control data DOC_CLR, DOC_FMR, DOC_FLR, DOC_CLS,DOC_FMS, DOC_FCS and DOC_FLS for document objects. Furthermore, the RM12 uses a set of the control data EML_CLR, EML_FMR, EML_CLS, EML_FMS andEML_FCS for email. Furthermore, the WM 13 uses a set of the control dataPRC_CLR, PRC_FMR, PRC_CLS, PRC_FMS and PRC_FCS for business processes, aset of the control data TSK_CLR, TSK_FMR, TSK_CLS, TSK_FMS and TSK_FCSfor tasks, and a set of the control data PWS_CLR, PWS_FMR, PWS_CLS,PWS_FMS and PWS_FCS for process work sheet classes. Furthermore, the PW14 uses a set of the control data PRJ_CLR, PRJ_FMR, PRJ_CLS, PRJ_FMS andPRJ_FCS for projects, a set of the control data TSK_CLR, TSK_FMR,TSK_CLS, TSK_FMS and TSK_FCS for tasks, and a set of the control dataPWS_CLR, PWS_FMR, PWS_CLS, PWS_FMS and PWS_FCS for process work sheetclasses.

Furthermore, the OM 11, RM 12, WM 13 and PM 14 provide the functions ofnewly registering or altering control data corresponding to the objecttypes handled by these managers to users having the authorization toregister such control data. Furthermore, although this is not shown inFIG. 5, the AM 15 provides the functions of newly registering oraltering all of the abovementioned control data to users having theauthorization to register such control data. Furthermore, the OM 11, RM12, WM 13 and PM 14 respectively refer to the abovementioned controldata and control the operations of the objects by the users (i.e., theflow of information among users).

Concrete examples of the control of object operations performed by theOM 11, RM 12, WM 13 and PM 14 on the basis of the abovementioned controldata will be described below. In the first place, the control performedby the OM 11 will be described.

FIG. 56 shows examples of the structures of the document classregistration data DOC_CLR, document form registration data DOC_FMR andocument folder registration data DOC_FLR used by the OM 11 in order tocontrol the operations of document objects. FIG. 57 shows examples ofthe document class security setting data DOC_CLS, document form securitysetting data DOC_FMS, document function security setting data DOC_FCSand document folder security setting data DOC_FLS. Furthermore, FIG. 58shows examples of the structures of the document administration tableDOC_ADT, annotation administration table ANT_ADT and work listadministration table WKL_ADT. FIG. 59 shows the flow of an example ofthe document object operation control performed by the OM 11. FIG. 60shows an example of the GUI window that is provided by the OM 11 inorder to display document objects. FIG. 61 shows the flow of an exampleof the control used to alter the forms of document objects performed bythe OM 11. FIG. 62 shows the flow of an example of the control of fileoperations within the document objects performed by the OM 11.

As is shown in FIG. 56, the names of one or more classes (names ofattribute items; ordinarily a plurality of names) CLS_a, CLS_b, CLS_c, .. . possessed by the document objects are registered in the documentclass registration data DOC_CLR; these class names can be arbitrarilydefined by users who have the authorization for this. For example, theinitial class name CLS_a can be defined as “subject field”, the nextclass name CLS_b can be defined as “supervising section name”, and thethird class name CLS_c can be defined as “key words”. Furthermore, theinput method for the respective class values (i.e., the method used bythe user to input the concrete contents of the respective classes whencreating concrete document objects) is also registered in this tableDOC_CLR; this can also be arbitrarily defined by users who have theauthorization for this. For example, the input method called “text box”refers to an input method in which the class values (contents) are inputby typing an arbitrary text using a text box that is displayed to theside of the class name in the GUI window used to create document objects(for instance, several classes such as “details” and “request” usingsuch a text box input method are shown as examples in the form 121 shownin FIG. 44). Furthermore, the input methods of “combo box”, “radiobutton” and “check box” respectively refer to input methods in whicharbitrary selection branches constituting the class values (contents)are selected using a radio button, check box or combo box used to selectany of a plurality of selection branches that are displayed alongsidethe class name. Furthermore, in the input methods of “combo box”, “radiobutton”, “check box” and the like, data for one or more selectionbranches OPT_a, OPT_b, . . . is provided, and these selection branchescan also be arbitrarily defined by users having the properauthorization. For example, the selection branches of “large”,“intermediate” and “small” can be defined as selection branches for the“radio button” input method of the class name “degree of importance”.

As is shown in FIG. 56, one or more form names (ordinarily a pluralityof form names) FRM_a, FRM_b, FRM_c, . . . possessed by the documentobjects, and one or more class names possessed by each form name, areregistered in the document form registration data DOC_FMR, and theseform names and class names can be arbitrarily defined by users havingthe proper authorization. In the example shown in FIG. 56, the form“FRM_a” has the three classes “CLS_a”, “CLS_b” and “CLS_c”.

As is shown in FIG. 56, the names of all of the folders FCL_a, FLC_b, .. . in which document objects are stored, and the names of folderspositioned above these respective folders, are registered in thedocument folder registration data DOC_FLR; in this way, the hierarchicalstructure of the folders is defined. Each time that the user creates,alters, deletes or moves a folder using the OM 11, the OM 11automatically updates the document folder registration data DOC_FLR.

As is shown in FIG. 57, class names selected from the document classregistration data DOC_CLR that can be accessed by each of a plurality ofusers USR_a, USR_b, . . . (there is also of course a table in whichthese users are registered; however, a description of this table isomitted) are registered beforehand in the documents class securitysetting data DOC_CLS; these class names can also be arbitrarily definedby users having the proper authorization. The respective users cannotaccess classes that are not registered in this table DOC_CLS. In theexample shown in FIG. 57, the user “USR_a” can access the classes“CLS_a”, “CLS_b” and “CLS_c”, but cannot access the other classes.

In the example shown in FIG. 57, form names selected from the documentform registration data DOC_FMR that can be accessed by each of aplurality of users USR_a, USR_b, . . . are registered in the documentform security setting data DOC_FMS; these form names can also bearbitrarily defined by users having the proper authorization. Therespective users cannot access forms that are not registered in thistable DOC_FMS. In the example shown in FIG. 57, the user “USR_a” canaccess the forms “FRM_aa”, “FRM_ab” and “FRM_ac”, but cannot access theother forms.

As is shown in FIG. 57, the names of functions possessed by the OM 11that can be accessed by each of a plurality of users USR_a, USR_b, . . .are registered in the document function security setting data DOC_FCS;these function names can also be arbitrarily defined by users having theproper authorization. The respective users cannot access functions thatare not registered in this table DOC_FMS. In the example shown in FIG.57, the user “USR_a” can access the functions “FNC_aa”, “FNC_ab” and“FNC_ac”, but cannot access the other functions.

As is shown in FIG. 57, folder names selected from the document folderdata DOC_FLR that can be accessed by each of a plurality of users USR_a,USR_b, . . . are registered in the document folder security setting dataDOC_FLS; these folder names can also be arbitrarily defined by usershaving the proper authorization. The respective users cannot accessfolders that are not registered in the table DOC_FMS. In the exampleshown in FIG. 57, the user “USR_a” can access the folders “FLD_a”,“FLD_b” and “FLD_c”, but cannot access the other folders.

As shown in FIG. 58, object definition data defining the documentobjects is registered for all of the document objects (excluding theannotation objects) in the document administration table DOC_ADT; thecontents of this data can be arbitrarily defined by the users whocreated the document objects. In FIG. 58, each row in the documentadministration table DOC_ADT expresses object definition data for one ofthe document objects. As is shown in the figure, the object definitiondata for each document object is data in which set values are definedfor items such as “document ID”, “document name”, “type”, “file”, “CLS_avalue”, “CLS_b value”, “author”, “creation date and time” and the like.Here, one type among the types single sheet (SS), multi-sheet (MS),multi-document (MD), multi-representation (MR) and registered (RG)described with reference to FIG. 4, which is given to the documentobject, is set in the item “type”. In the example shown in FIG. 58, thetype of the initial document object is “MD”, and the type of the seconddocument object is “MS”. The name of the folder in which the documentobject is stored is set in the item “folder name”. Reference values,e.g., full-path file names, for one or more files associated with thedocument object (i.e., handles as the document object) are set in theitem “file”. However, in cases where the “type” is RG, nothing is set in“file”. In the example shown in FIG. 58, the initial document object isassociated with a plurality of files “¥FLD_i¥FLD_j¥FIL_k”,“¥FLD_p¥FIL_q, . . . . User input values (e.g., text, selected branchesand the like) for all of the class names CLS_a, CLS_b, . . . defined inthe document class registration data DOC_CLR shown in FIG. 56 are set inthe items “CLS_a value” and “CLS_b value”. In the Example shown in FIG.58, the value of “system outline” is set in the initial class “CLS_a”(e.g., “subject field”) in the case of the initial document object, andthe value of “system plans” is set in the next class “CLS_b” (e.g.,“supervising section”).

As is shown in FIG. 58, object definition data defining the AN object isregistered for all of the annotation (AN) objects in the annotationadministration table ANT_ADT; the contents of this object definitiondata can be arbitrarily set by the users who created the AN objects. InFIG. 58, each row of the annotation administration table ANT_ADTexpresses object definition data for one of the AN objects. As is shownin the figure, set values are defined for items such as “annotation ID”,“annotation name”, “document ID”, “comments”, “file” author”, “creationdate and time”, “approver”, “approval date and time” and the like in theobject definition data for each AN object. Here, a reference value,e.g., document ID, for other document objects to which the AN object isappended is set in the item “document ID”. In the example shown in FIG.58, the initial AN object is appended to the document object “DID_aa”.Reference values, e.g., full-path file names, for one or more filesassociated with the AN object (i.e., handled as the AN object) are setin the item “file”.

As is shown in FIG. 58, object definition data defining the WKL isregistered in the work list administration table WKL_ADT for all of thework lists (WKL); the contents of this data can be arbitrarily definedby the users who created the WKL. In FIG. 58, each row in the WKLadministration table ANT_ADT expresses object definition data for one ofthe WKL. As is shown in the figure, set values for items such as “worklist ID”, “work list name”, “document ID”, “author”, “creation date andtime” and the like are defined in the respective sets of WKL definitiondata. Here, a reference value, e.g., document ID, for all of thedocument objects contained in the WKL is set in the item “document ID”.

FIG. 59 shows the flow of the control of document object operationsperformed by the OM 11.

As is shown in FIG. 59, a certain user opens the OM 11 in step S11.Consequently, in step S12, the OM 11 grasps the hierarchical structureof the folders relating to the document object by referring to thedocument folder registration data DOC_FLR shown in FIG. 56, grasps thefolders that can be accessed and folders that cannot be accessed by theuser by referring to the document folder security setting data DOC_FLSshown in FIG. 57, and displays a folder structure in which the foldersthat can be accessed and folders that cannot be accessed aredistinguished by color in the folder browser window of a specified GUIwindow. FIG. 60 shows an example of this GUI window; the abovementionedfolder browser window 100 is displayed on the left side.

Referring again to FIG. 59, the user selects the folder that he wishesto open from the folder browser window 100 in step S13. Consequently, instep S14, the OM 11 refers to the document folder security setting dataDOC_FLS shown in FIG. 57, and opens the selected folder only in caseswhere the user is allowed access to the selected folder. Then, in stepS15, a list of the document objects in the opened folder is displayed inthe abovementioned GUI window. For example, as is shown in FIG. 40, theabovementioned document object list 106 is displayed in the main window101 in the center.

Subsequently, in step S16, the user selects the document object that hewishes to open from displayed document list. Consequently, in step S17,the OM 11 refers to the document class security setting data DOC_CLS anddocument form security setting data DOC_FMS shown in FIG. 57, and graspsthe classes that can be accessed by the user and that are contained in aspecified default form that can be accessed by the user. Next, the OM 11refers to the object definition data of the selected document object inthe document administration table DOC_ADT shown in FIG. 58, reads thevalues of the abovementioned grasped classes, and crates classinformation (a list of the attributes of the document object) only fromthe read class values. Furthermore, in step S18, the OM 11 refers to thedocument form security setting data DOC_FMS shown in FIG. 57, andcreates a form selection combo box only from the form names that can beaccessed by the user. Furthermore, in step S19, the OM 11 refers to theobject definition data of the selected document object in the documentadministration table DOC_ADT shown in FIG. 58, and creates a list offiles associated with the document object (i.e., contained in thedocument object). Furthermore, in step S20, the OM 11 refers to theannotation registration table ANT_ADT shown in FIG. 58, and creates alist of the annotation objects associated with the document object.Then, in step S21, the OM 11 displays the created class information,form selection combo box, file list and annotation list in theabovementioned GUI window. For example, as is shown in FIG. 60, theclass information 131, form selection combo box 133, file list 135 andannotation list 137 for the selected document object are displayed inthe main window 101 in the center.

Furthermore, in cases where it is desired to display a work list, theuser operates the work list button 111 in the GUI window shown in FIG.40. When this is done, the OM 11 displays a list of the work lists thatare currently present. When the user selects the desired work list fromthis list of work lists, the OM 11 displays a list of the documentobjects contained in the selected work list. This list of documentobjects has a construction similar to that of the list of documentobjects 106 in the selected folder shown in FIG. 40. When the userselects a document object that is to be opened from this list ofdocument object, the OM 11 performs the processing of steps S17 throughS21 shown in the abovementioned FIG. 59.

Referring again to FIG. 59, the user selects an arbitrary function ofthe OM 11 in step S22 (for example, modification of the class values ofthe document object, addition of files or annotations to the documentobject, opening of a file in the file list 135 shown in FIG. 60, editingor deletion of such a file, opening of an annotation in the annotationlist 137, editing, deletion or approval of such an annotation, or thelike). Consequently, in step S23, the OM 11 refers to the documentfunction security setting data DOC_FCS shown in FIG. 57, and performsthe selected function only in cases where the user is allowed access tothis selected function.

Furthermore, in step S25 shown in FIG. 59, the user request the additionof a document object to the opened folder. Consequently, in step S26,the OM 11 refers to the function security setting data DOC_FCS shown inFIG. 57, and, only in cases where the user is allowed access to thefunction of document addition, performs the function of documentaddition and displays a document registration window used to registerthe new document object in (for example) the main window 101 inside theGUI window shown in FIG. 60. In step S27, the user inputs the objectname, type, folder, file, class values of all of the classes (all of theclasses defined in the document class registration data DOC_CLR shown inFIG. 56) and the like for the document object that is to be added intothe abovementioned document registration window, and instructs the OM 11to perform registration. Consequently, in step S28, the OM 11 createsobject definition data for the new document object on the basis of theinput values input into the document registration window by the user,and adds and registers this in the document administration table DOC_ADTshown in FIG. 58.

Furthermore, the OM 11 performs controls such as that shown for examplein FIG. 61 in cases where the user alters a form using the formselection combo box 133 in the main window 101 displaying the contentsof a certain document object as shown in FIG. 60.

In FIG. 61, the user alters the form in step S31. Consequently, in stepS32, the OM 11 refers to the document class security setting dataDOC_CLS and document form security setting data DOC_FMS shown in FIG.57, and grasps classes that can be accessed by the user, and that arecontained in the altered form. Next, the OM 11 refers to the objectdefinition data for the selected document object in the documentadministration table DOC_ADT shown in FIG. 58, reads the values of theabovementioned grasped classes (i.e., the values of classes that can beaccessed by the user in the form following modification), and createsclass information suited to the altered form only from the read classvalues. Then, in step S33, the OM 11 updates the class information 131displayed in the main window 101 shown in FIG. 60 to class informationthat is suited to the form following modification.

Furthermore, in cases where the user performed file operations (e.g.,opening, addition or deletion of files, or addition or deletion ofannotations) in the main window 101 displaying the contents of a certaindocument object as shown in FIG. 60, the OM 11 performs the controlshown in FIG. 62.

In FIG. 62, the user selects a file that is to opened from the file list135 in step S41. Consequently, in step S42, the OM 11 refers to thedocument function security setting data DIC_FCS shown in FIG. 57, checkswhether the user is allowed to perform the function of opening files,and performs this file opening function only in cases where the user ispermitted to use this function. In the case of this file openingfunction, the OM 11 checks the type of the document object in step S43,and in cases where this type is MR and SS, the OM 11 opens not only theselected file, but also all of the files associated with the documentobject, in step S44. On the other hand, in cases where the type is otherthan MR, the OM 11 opens only the selected file in step S45.

In step S51, the user selects file addition using the file additionbutton 139. Consequently, in step S51, the OM 11 refers to the documentfunction security setting data DIC_FCS shown in FIG. 57, and checkswhether or not the user is allowed to perform the function of fileaddition. Then, the OM 11 performs the function of file addition only incases where this function is allowed. In the case of the file additionfunction, the OM 11, in step S53, additionally registers the file nameof the file designated by the user in the object definition data for thedocument object in the document administration table DOC_ADT shown inFIG. 58, and additionally registers the file name of the file designatedby the user in the file list 135 shown in FIG. 60. Furthermore, in stepS54, the OM 11 checks the type of the document object, and in caseswhere the type is SS, the OM 11 alters the type to MR in step S55; onthe other hand, in cases where the type is RG, the OM 11 alters the typeto SS in step S56, and in cases where the type is some other type, theOM 11 does not alter the type.

In step S61, the user requests the deletion of a certain file in thefile list 135. Consequently, in step S62, the OM 11 refers to thedocument function security setting data DIC_FCS shown in FIG. 57 andchecks whether the user is allowed access to the function of filedeletion. The OM 11 then performs the function of file deletion only incases where access to this function is allowed. In the file deletionfunction, the OM 11, in step S63, deletes the full-path file name of thefile designated by the user from the object definition data of thedocument object in the document administration table DOC_ADT shown inFIG. 58, and deletes the file name of the file designated by the userfrom the file list 135 shown in FIG. 60. Furthermore, in step S64, theOM 11 checks the type of the document object, and in cases where thetype is SS, the OM 11 alters the type to RG MR in step S65. Furthermore,in cases where the type is MD or MR, the OM 11 checks the number ofremaining files in step S66, and if the number of remaining files is 1,the OM 11 alters the type to SS in step S67. In cases where the type issome other type, the OM 11 does not alter the type.

In step S71, the user requests the addition or deletion of an annotation(AN) object. Consequently, in step S72, the OM 11 refers to the documentfunction security setting data DIC_FCS shown in FIG. 57, and checkswhether or not the user is allowed access to the function of AN objectaddition or deletion. Then, the OM 11 performs the function of AN objectaddition or deletion only in cases where access to this function isallowed. In the function of AN object addition or deletion, the OM 11,in step S73, adds or deletes the annotation definition data designatedby the user in the annotation administration table ANT_ADT shown in FIG.58, and adds or deletes the information of this annotation in theannotation list 137 shown in FIG. 60.

The principle of the method of control of operations relating todocument objects performed by the OM 11 as described above can also beapplied to the control of operations relating to email performed by theRM 12, the control of operations relating to business processesperformed by the WM 13, and the control of operations relating toprojects, tasks, process work sheets and deliverables performed by thePM 14.

Next, the control of operations relating to email performed by the RM 12will be described with a special focus on the control that is peculiarto email.

FIG. 63 shows an example of the structure of the email administrationtable EML_ADT. FIG. 64 shows the flow of an example of the control ofemail operations performed by the RM 12. FIG. 65 shows an example of theGUI window that is provided by the RM 12 for the purpose of displayingemail.

With regard to email, as was already described with reference to FIG.55, control data such as email class registration data EML_CLR, emailform registration data EML_FMR, email folder registration data EML_FLR,email class security setting data EML_CLS, email form security settingdata EML_FMS, email function security setting data EML_FCS, email foldersecurity setting data EML_FLS and the like is provided. These sets ofcontrol data have respective data structures that are basically similarto those of the same types of control data relating to document objectsshown in FIGS. 56 and 57, i.e., document class registration dataDOC_CLR, document form registration data DOC_FMR, document folderregistration data DOC_FLR, document class security setting data DOC_CLS,document form security setting data DOC_FMS, document function securitysetting data DOC_FCS and document folder security setting data DOC_FLS.

Furthermore, as is shown in FIG. 63, object definition data definingemail is registered for all of the email in the email administrationtable EML_ADT, and the contents of this data can be arbitrarily definedby the users who created the email. In FIG. 63, each row in the emailadministration table EML_ADT expresses object definition data for one ofthe emails. As is shown in the figure, set values for items such as“mail ID”, “title”, “type”, “transmission source”, “address”, “CC”,“reply deadline”, “CLS_a value”, . . . . , “message”, “attachments”,“permission to send”, “communications group limitation”, “printinstructions”, “archive instructions”, “trunk instructions”,“transmission date and time”, “status” and the like are defined in theobject definition data for each email. Here, the items “mail ID”,“title”, “transmission source”, “address” and “CC” have the samemeanings as similar data contained in the headers of common universallyknown email. One type selected from the types of formal mail (FM),informal mail (IFM) and bulletin mail (BM) (described with reference toFIG. 5), which is given to each email, is set in the item “type”. In theexample shown in FIG. 58, the type of the initial email is “FM”, and thetype of the second email is “IFM”. Furthermore, the deadline by whichthe receiver is supposed to reply to this email is set in the item“reply deadline”. The value of “reply deadline” is set only in caseswhere the type of the email is “FM”; this value is not set in the caseof other types. User input values (e.g., text, selected selection branchor the like) for all of the class names CLS_a, . . . defined in theemail class registration data EML_CLR (which has the same structure asthe document class registration data DOC_CLR shown in FIG. 56) are setin the items “CLS_a value”, . . . . The main text message of the emailis set in the item “message”. Reference values for data attached to theemail are set in the item “attachments”. Data that can be attachedincludes files and various types of objects. In cases where files areattached, for example, the full-path file names of the files can be setas the reference values; furthermore, in cases where objects areattached, for example, the object ID of the objects can be set as thereference values. In the example shown in FIG. 63, the file“¥FOL_x¥FIL_a”, the document object “DID a”, the work list “WKL_a”, thetask list “TKL_a” and the like are attached to the initial email. Theflag values (ON or OFF) of the forwarding approval (AF) andcommunications group limitation (LG) described with reference to FIG. 5are set in the items “forwarding approval” and “communications grouplimitation”. The presence or absence (ON or OFF) of instructions forentering the email objects (or not entering the email objects) infolders that store specified objects of printing, folders for objectarchives and folders for object distribution are set in the items “printinstructions”, “archive instructions” and “trunk instructions”. Thestatus relating to the relationship between the abovementioned replydeadline and the current point in time (deadline expired, beforedeadline, deadline close or the like) is automatically set in the item“status”.

FIG. 64 shows the flow of an example of the control of email operationsperformed by the RM 12.

As is shown in FIG. 64, the user opens the RM 12 in step S81.Consequently, in step S82, the RM 12 refers to the email folderregistration table EML_FLR, and grasps the hierarchical structure offolders relating to the email; furthermore, the RM 12 refers to theemail folder security setting table EML_FLS, and grasps the folders thatcan or cannot be accessed by the user. Then, the RM 12 displays an emailfolder structure in which folders that can be accessed by the user andfolders that cannot be accessed by the user are distinguished by colorin the folder browser window of a specified GUI window. FIG. 65 shows anexample of this GUI window; the abovementioned email folder structure isdisplayed in the folder browser window 700 on the left side.

In step S83, the user selects a folder for mail creation of the desiredtype (FM, IFM or BM) in the folder browser window 700 shown in FIG. 65.For instance, in the example shown in FIG. 65, the folders “formal”“informal” and “bulletin” inside the folder “compose” are respectivelyfolders that are used to create formal mail (FM), informal mail (IFM)and bulletin mail (BM). Consequently, in step S84, the RM 12 displaysthe mail creation window used to create mail of the type selected by theuser in the main window 701 inside the GUI window shown in FIG. 65(however, in the example shown in FIG. 65, the contents of the receivedmail displayed in step S92 described later are displayed in the mainwindow 701 rather than the mail creation window). In step S85, the userinputs the title, address, message, reply deadline, attachments, varioustypes of control instructions (forwarding approval, communications grouplimitation, print instructions, archive instructions, trunk instructionsor the like) and all of the class values into the displayed mailcreation window. In step S86, the user requests mail transmission.Consequently, in step S87, the RM 12 creates new mail object definitiondata on the basis of the abovementioned information input by the user,registers this data in the email administration table EML_ADT, andtransmits the email to the address.

In step S88, the user selects a reception box folder for mail of anarbitrary type in the folder browser window 700 shown in FIG. 65. In theexample shown in FIG. 65, the folders “formal”, “informal” and“bulletin” inside the folder “inbox” are respectively reception boxfolders for formal mail (FM), informal mail (IFM) and bulletin mail(BM). Consequently, in step S89, the RM 12 displays a list of receivedmail of the type selected by the user in the main window 701 shown inFIG. 65. In this case, the RM 12 refers to the object definition data ofthe received mail in the email administration table EML_ADT, acquiresthe status of the respective received mails, and displays the acquiredstatus in the received email list using colored labels. In step S90, theuser selects an arbitrary received mail from the received mail list.Consequently, in step S91, the RM 12 refers to the email class securitysetting data EML_CLS and email form security setting data EML_FMS, andgrasps the classes contained in the default form that can be utilized bythe user, and that can be accessed by the user. Then, the RM 12 acquiresobject definition data for the selected received mail in the emailadministration table EML_ADT, and creates class information from onlythe class values that can be accessed by the user on the basis of thisdata. Furthermore, the RM 12 refers to the email form security settingdata EML_FMS, and creates a form selection combo box for the selectionof accessible forms by the user. Then, in step S92, the RM 12 displaysthe class information, form selection combo box and information acquiredfrom other object definition data in the main window 701 shown in FIG.65. In the example shown in FIG. 65, a table 711 expressing headerinformation and class information, a form selection combo box 713, areply deadline 715, a colored label 717 indicating the status, aforwarding approval (AF) flag value 719, a communications grouplimitation (LG) flag value 721, an attachment list 723, a main textmessage 725 and the like are displayed inside the main window 701.Furthermore, the RM 12 forwards the selected received mail to thedesignated folder in accordance with the values of the printinstructions, archive instructions and trunk instructions in the objectdefinition data for the selected received mail.

Subsequently, in step S93, the user requests the reply to, or forwardingof, the selected received mail. Consequently, in step S94, the RM 12controls the reply to or forwarding of the received mail on the basis ofthe forwarding approval (AF) flag value 719 or communications grouplimitation (LG) flag value 721 in the object definition data of theselected received mail.

In step S95, the user selects an arbitrary function of the RM 12.Consequently, in step S96, the RM 12 refers to the email functionsecurity setting data EML_FCS, and performs the selected function onlyin cases where the user is allowed access to the selected function.

Next, the control of operations relating to business processes and tasksthat is performed by the WM 13 will be described.

FIG. 66 shows an example of the structure of the process administrationtable PRC_ADT. FIG. 67 shows an example of the structure of the taskadministration table TSK_ADT.

With regard to business processes, as was already described withreference to FIG. 55, process class registration data PRC_CLR, processform registration data PRC_FMR, process folder registration dataPRC_FLR, process class security setting data PRC_CLS, process formsecurity setting data PRC_FMS, process function security setting dataPRC_FCS and process folder security setting data PRC_FLS are provided.Furthermore, with regard to tasks, task class registration data TSK_CLR,task form registration data TSK_FMR, task class security setting dataTSK_CLS, task form security setting data TSK_FMS and task functionsecurity setting data TSK_FCS are provided. The structures of these setsof control data are basically similar to the structures of control dataof the same types relating to document objects shown in FIGS. 56 and 57,i.e., document class registration data DOC_CLR, document formregistration data DOC_FMR, document folder registration data DOC_FLR,document class security setting data DOC_CLS, document form securitysetting data DOC_FMS, document function security setting data DOC_FCSand document folder security setting data DOC_FLS.

Furthermore, as is shown in FIG. 66, object definition data defining thebusiness processes is registered in the process administration tablePRC_ADT for all of the business processes; the contents of this data canbe arbitrarily defined by the users who created the business processes.In FIG. 66, each line in the process administration table PRC_ADTexpresses object definition data for one of the business processes. Asis shown in the figure, set values for items such as “process ID”,“process name”, “process form”, “CLS_a value”, “CLS_b value”, . . .“author”, “creation date and time”, “workflow” and the like are definedin the object definition data for each business process. Here, the namesof one or more forms (process forms) used as process work sheets(reports) in each business process are set in the item “process form”;these are forms that are selected from a plurality of process forms(“approval”, “default” and “specification” in the example shown in FIG.9) that have been prepared beforehand using the form selection tools513, 514 and 515 in the process registration window shown in FIG. 9 bythe user who created the business process. Here, the plurality ofprocess forms (process work sheet forms) and class names (process worksheet classes) that have been prepared beforehand are defined in theprocess work sheet form registration data PWS_FMR and process work sheetclass registration data PWS_CLR shown in FIG. 55; these can also befreely defined by users having the authorization to register processwork sheets. Input values (e.g., text, selected selection branch or thelike) input by the user for all of the class names CLS_a, . . . definedin the process class registration data PRC_CLR (which has the samestructure as the document class registration data DOC_CLR) shown in FIG.56) are set in the items “CLS_a value”, . . . . The data of a workflowmodel for the business process (constructed using the GUI windows shownfor example in FIGS. 13 through 16) is set in the item “workflow”. Forexample, as is shown in FIG. 66, the data of this workflow model isconstructed from data expressing all of the stages possessed by theworkflow model, the names of all of the sections assigned to therespective stages, links of the respective sections of the respectivestages with sections of previous stages and the like (the data exampleshown in FIG. 66 expresses a workflow model example indicated insidedotted-line frames).

Furthermore, as is shown in FIG. 67, object definition data defining thetasks is registered for all of the tasks in the task administrationtable TSK_ADT; the contents of this data can be arbitrarily defined bythe users who created the tasks. In FIG. 67, each row in the taskadministration table TSK_ADT expresses object definition data for one ofthe tasks. As is shown in the figure, set values for items such as “taskID”, “task name”, “CLS_a value”, “CLS_b value”, . . . , “template”,“author”, “creation date and time” and the like are defined in theobject definition data for each task. Here, the input values (e.g.,text, selected selection branch or the like) input by the user for allof the class names CLS_a, . . . defined in the task class registrationdata TSK_CLR (which has the same structure as the document classregistration data DOC_CLR shown in FIG. 56) are set in the items“CLS_a”, “CLS_b”, . . . . Furthermore, reference values, e.g., documentID, for one or more document objects (templates) used as a standardmodel of deliverables to which reference can be made when the userperforming the task creates document objects that constitutedeliverables are set in the item “template”.

When operations such as the display, creation, modification, deletion ofbusiness processes and tasks (as well as various other types ofoperations) are performed, the WM 13 can control the operations of thesebusiness processes and tasks using data relating to the abovementionedbusiness processes and tasks according to a principle similar to that ofthe control performed by the OM 11 with respect to document objects.

Next, the control of operations relating to projects that is performedby the PM 14, and especially the control of operations relating to taskswithin such projects, will be described.

FIGS. 68 and 69 are connected, and show an example of the structure ofthe project administration table PRC_ADT. FIG. 70 shows an example ofthe structure of the task list administration table TKL_ADT. FIG. 71shows the flow of an example of the control of operations relating totasks within projects that is performed by the PM 14.

In regard to projects, s was already described with reference to FIG.55, project class registration data PRJ_CLR, project form registrationdata PRJ_FMR, project folder registration data PRJ_FLR, project classsecurity setting data PRJ_CLS, project form security setting dataPRJ_FMS, projection function security setting data PRJ_FCS and projectfolder security setting data PRJ_FLS are provided. The structures ofthese sets of control data are basically similar to those of the controldata of the same types relating to document objects shown in FIGS. 56and 57, i.e., document class registration data DOC_CLR, document formregistration data DOC_FMR, document folder registration data DOC_FLR,document class security setting data DOC_CLS, document form securitysetting data DOC_FMS, document function security setting data DOC_FCSand document folder security setting data DOC_FLS.

Furthermore, as was already described with reference to FIG. 55, processwork sheet class registration data PWS_CLR, process work sheet formregistration data PWS_FMR, process work sheet class security settingdata PWS_CLS, process work sheet form security setting data PWS_FMS andprocess work sheet function security setting data PWS_FCS are providedfor process work sheets (reports that are transferred from user to userin the process of performing business processes within a certainproject). The structures of these sets of control data are alsobasically similar to those of the control data of the same typesrelating to document objects shown in FIGS. 56 and 57, i.e., documentclass registration data DOC_CLR, document form registration dataDOC_FMR, document folder registration data DOC_FLR, document classsecurity setting data DOC_CLS, document form security setting dataDOC_FMS, document function security setting data DOC_FCS and documentfolder security setting data DOC_FLS.

As is shown in FIG. 68, object definition data defining the projects isregistered in the project administration table PRJ_ADT for all of theprojects; the contents of this data can be arbitrarily defined by theusers who created the projects. In FIG. 68, each line in the projectadministration table PRJ_ADT expresses object definition data for one ofthe projects. As is shown in the figure, set values for items such as“project ID”, “project name”, “CLS_a value”, “CLS_b value”, . . .“author”, “creation date and time”, “project structure” and the like aredefined in the object definition data for each project. Here, the inputvalues (e.g., text, selected selection branch or the like) input by theuser for all of the class names CLS_a, . . . defined in the projectclass registration data PRJ_CLR (which has the same structure as thedocument class registration data DOC_CLR shown in FIG. 56) are set inthe items “CLS_a”, “CLS_b”, . . . .

Data expressing the structure of the project is set in the item “projectstructure”. As is shown in FIG. 68, set values for the items “process”,“work sheet” and “section” are included in this project structure data.Reference values, e.g., process ID, for all of the business processes(workflow models) assigned to the project are set in the item “process”.Data for one or more process work sheets (reports) created by the userin the respective execution of all of the business processes assigned tothe project is set in the item “work sheet”. The concrete constructionof this process work sheet data will be described later with referenceto FIG. 69. Reference values, e.g., section ID, for all of the sectionsincluded in the workflow model of the business process, and data for theitem “phase” for each section, are set for all of the business processesassigned to the project in the item “section”. The data for the item“phase” includes the names of all of the phases set for the businessprocess, and data for the item “task” for each phase. As is shown inFIG. 69, the data for the item “task” includes set values for items suchas reference values, e.g., task ID, for all of the tasks assigned to thephases of the business process, as well as “sub-tasks”, “employees”,“role”, “person responsible”, “expected start time”, “expected endtime”, “period”, “safety rate”, “actual start time”, “actual end time”,“status” and the like for each task.

Reference values, e.g., task ID of sub-tasks, for all of the sub-tasksassigned to each task, and data for the item “deliverables” for eachtask, are set in the item “sub-tasks” for each task. Data for the item“deliverables” for each task includes reference values, e.g., documentID, for all of the document objects constituting deliverables created bythe user performing the sub-task. Furthermore, employees, roles, personsresponsible, expected start time, expected end time, period, safetyrate, actual start time and actual end time that are assigned or set foreach task of each phase of the project are set in the items “employees”,“role”, “person responsible”, “expected start time”, “expected endtime”, “period”, “safety rate”, “actual start time” and “actual endtime” for each task. Furthermore, status data expressing the start, endor rate of progress of each task is automatically set by the PM 14 (aswill be described later) in the item “status” for each task.

As is shown in FIG. 69, data defining all of the process work sheetscreated in the business process is included in the process work sheetdata set in the item “work sheet” for each business process shown inFIG. 68. The definition data for each process work sheet includes setvalues for items such as “process form”, “CLS_a value”, “CLS_b value”, .. . , “attachments” and the like. Here, the names of the process formsused in the creation of the process work sheet are set in the item“process form”. The input values (e.g., text, selected selection branchor the like) input by the user for all of the class names CLS_a, . . .defined in the process work sheet class registration data PWS_CLR (whichhas the same structure as the document class registration data DOC_CLRshown in FIG. 56) are set in the items “CLS_a”, “CLS_b”, . . . .Reference values, e.g., full-path file names or object ID, for files orobjects that are attached to the process work sheet are set in the item“attachments”.

Furthermore, as is shown in FIG. 70, object definition data defining thetask lists is registered for all of the task lists in the task listadministration table TKL_ADT; the contents of this data areautomatically defined when the PM 14 creates the task lists as shown inFIG. 45, or when the task lists are updated in step S117 shown in FIG.71 (described later). In FIG. 70, each row in the task listadministration table TSK_ADT expresses object definition data for one ofthe task lists. As is shown in the figure, set values for items such as“task list ID”, “task list name”, “user”, “task”, “creation date andtime” and the like are defined in the object definition data for eachtask list. Here, reference values to the users (sections or employees)using the task lists, e.g., user ID, are set in the item “user”.Reference values for all of the tasks included in the task list, e.g.,task ID, are set in the item “task”.

FIG. 71 shows the flow of an example of the control of task operationswithin the project that is performed by the PM 14.

In FIG. 71, the user selects a desired task belonging to a desiredbusiness process of a desired project from the GUI window of the OM 11(shown in FIG. 41) in step S101. Consequently, in step S102, the PM 14displays details of the selected task in the GUI window of the OM 11 asshown in FIGS. 42 and 43. In this case, the PM 14 refers to the taskclass security setting data TSK_CLS shown in FIG. 55, and grasps theclasses that can be accessed by the user. Furthermore, the PM 14acquires the class values of the abovementioned accessible classes forthe abovementioned selected task from the object definition data for theabovementioned desired project in the project administration dataPRJ_ADT shown in FIGS. 68 and 69, and displays class informationcomprising these class values in the class detail table 115 of the GUIwindow shown in FIG. 42. Furthermore, the PM 14 displays the templatesused in the task defined in the task administration table TSK_ADT shownin FIG. 67 in the task status table 117 inside the GUI window shown inFIG. 43. Furthermore, the PM 14 displays a list 118 of the process formsused in the business process defined in the process administration tablePRC_ADT shown in FIG. 66 in the GUI window shown in FIG. 43.

Referring again to FIG. 71, the user selects one of the templates in thetask status table 117 shown in FIG. 43 in step S103. Consequently, instep S104, the PM 14 opens the template selected by the user. In stepS105, the user refers to the opened template, and creates the documentobject constituting the deliverable of the task. In step S106, the userattaches the document object of the created deliverable to the projectby operating the task status table 117 shown in FIG. 43. Consequently,in step S107, the PM 14 stores the document object of the deliverable inthe deliverable folder DLV_FLD_a shown in FIG. 55; furthermore, the PM14 registers the document object of the deliverable in the objectdefinition data of the project in the project administration tablePRJ_ADT shown in FIGS. 68 and 69.

In step S108, the user selects one of the process forms from the processform list 118 shown in FIG. 43. Consequently, in step A109, the PM 14opens the work sheet input form 121 according to the selected processform in the GUI window as shown in FIG. 44. In this case, the PM 14refers to the process work sheet class registration data PWS_CLR,process work sheet form registration data PWS_FMR, process work sheetclass security setting data PWS_CLS and process work sheet form securitysetting data PWS_FMS shown in FIG. 55, and grasps the classes thatbelong to a specified default class that can be accessed by the user,and that are classes that can be accessed by the user; the PM 14 thendisplays tools (text box, radio button, check box, combo box or thelike) used to input these accessible class values in the work sheetinput form 121 shown in FIG. 44. Further, the PM 14 prepares a combo box123 for selecting a process work sheet form accessible by the user, anddisplays the same also in the work sheet input form 121 as shown in FIG.44. Furthermore, the PM 14 also displays a list 123 of attachments tothe process work sheet in the work sheet input form 121.

In step S110, the user inputs a report message into the work sheet inputform 121 shown in FIG. 44, and creates a process work sheet. In stepS111, the user (if necessary) attaches arbitrary files or objects to theprocess work sheet using the attachment list 123 shown in FIG. 44. Instep S112, user operates the submit button 124 shown in FIG. 44, andrequests submission of this process work sheet. Consequently, in stepS113, the PM 14 registers the process work sheet in the objectdefinition data of the project in the project administration tablePRJ_ADT shown in FIGS. 68 and 69.

In step S114, the user inputs the actual start time and actual end timefor the task displayed in FIG. 42. Consequently, in step S114, the PMrecognizes that the task has actually been started or completed, andregisters the actual start time or actual end time and status (start orend) of the task in the object definition data of the project in theproject administration table PRJ_ADT shown in FIGS. 68 and 69. Then, instep S116, the PM 14 refers to the object definition data of the projectin the project administration table PRJ_ADT shown in FIGS. 68 and 69,and checks whether or not all of the tasks of the section of the projecthave actually been completed. As a result, if all of the tasks of thesection of the projects have actually been completed, the task list ofthis section and the task list of the next section (which section is thenext section is understood from the workflow of the project in questionin the process administration table PRC_ADT shown in FIG. 66) areupdated in step S117 as shown in FIG. 45.

An embodiment of the present invention was described above. However,this embodiment is merely an example used to illustrate the presentinvention; the scope of the present invention is not limited to thisembodiment alone. Accordingly, the present invention can be worked invarious other aspects that involve no departure from the gist of theinvention.

1. A virtual knowledge management system using a computer, comprising: avirtual knowledge base which stores a plurality of objects that are dataentities for respective utilization by a plurality of users, and thatbelong to different object types, and control data that is providedcorresponding to each of said object types, and that relates to thecontrol of object operations performed by said users; and a managerwhich has a plurality of types of functions for respectively performinga plurality of types of object operations including the display andpreparation of said objects belonging to each object type in accordancewith requests from said users; wherein the respective functions of saidmanager control the respective operations for said objects belonging tothe respective object types in accordance with the control data of thecorresponding object types.
 2. The virtual knowledge management systemaccording to claim 1, wherein said manager further has functions forpreparing or altering said control data corresponding to the respectiveobject types in accordance with requests from said users.
 3. The virtualknowledge management system according to claim 1, wherein said controldata corresponding to the respective object types includes: classdefinition data which defines one or more classes possessed by saidobjects belonging to the respective object types; and class securitysetting data which defines the classes that can be accessed or thatcannot be accessed by the respective users among said one or moreclasses; said objects belonging to the respective object types havevalues of said one or more classes defined by said class definition datacorresponding to the respective object types; and the function used todisplay said objects inside said manager is arranged so that the valuesof classes that can be accessed by the respective users are selectedfrom the values of said one or more classes possessed by said objectsbelonging to the respective object types, and are displayed to therespective users, on the basis of said class security setting datacorresponding to the respective object types.
 4. The virtual knowledgemanagement system according to claim 1, wherein said control datacorresponding to the respective object types includes: folder definitiondata which defines one or more folders in which said objects belongingto the respective object types are stored; and folder security settingdata which defines the folders that can be accessed or that cannot beaccessed by the respective users among said one or more folders; saidmanager further has a folder operating function for operating said oneor more folders defined by said folder definition data corresponding tothe respective object types in accordance with requests from therespective users; and said folder display function is arranged so thatfolders are displayed with a distinction being made between folders thatcan be accessed and folders that cannot be accessed by the respectiveusers on the basis of said folder security setting data corresponding tothe respective object types, and so that only folders that can beaccessed by the respective users among said one or more folders that aredisplayed are opened in accordance with requests from the respectiveusers.
 5. The virtual knowledge management system according to claim 1,wherein said control data corresponding to the respective object typesincludes function security setting data which defines functions that canbe accessed or that cannot be accessed by the respective users amongsaid plurality of types of functions inside said manager; and the systemis arranged so that only the functions that are defined by said functionsecurity setting data corresponding to the respective object types asbeing accessible by the respective users, among said plurality of typesof functions for the respective object types inside said manager, can beoperated in accordance with requests from the respective users.
 6. Thevirtual knowledge management system according to claim 1, wherein saidobjects belonging to one of said object types are document objects whichcan be associated with document files; the respective document objectshave type data which indicates one type selected from a plurality ofspecified types differing in the numbers or types of associated documentfiles, and also have association data which indicates the associationwith one or more document files in cases where the document objects areassociated with said one or more document files; the function fordisplaying said document objects inside said manager displays the typesof the respective document objects on the basis of said type data of therespective document objects, and displays the document files associatedwith the respective document objects on the basis of said associationdata of the respective document objects, and opens said associateddocument files in accordance with requests from said users.
 7. Thevirtual knowledge management system according to claim 1, wherein saidobjects belonging to one of said object types are email messages; therespective email messages have type data which indicates one typeselected from a plurality of specified types differing in whether or notreplay deadline is set, and when said replay deadline is set, also havedeadline data indicating the replay deadline and status data whichindicates whether not the reply deadline has expired; the function fordisplaying said email messages inside said manager displays the typedata of the respective email messages and, when said email messages havethe replay deadline data and status data, also displays the replaydeadline and status of the respective email messages.
 8. The virtualknowledge management system according to claim 1, wherein said objectsbelonging to one of said object types are email messages; the respectiveemail messages have reply/forwarding control data which relates to thereply to, or forwarding of, the respective email messages; said managerhas a reply/forwarding function for replying to or forwarding said emailmessages in accordance with requests from said users, and saidreply/forwarding function is arranged so that this function controls thereply to or forwarding of the respective email messages on the basis ofsaid reply/forwarding control data possessed by the respective emailmessages.
 9. The virtual knowledge management system according to claim1, wherein said objects belonging to one of said object types arebusiness processes which respectively have one or more sets of workflowmodel data that respectively define the flow of work among a pluralityof users; said objects belonging to another one of said object types aretasks which have task data that defines the work that can be performedby said users said objects belonging to another one of said object typesare projects, these respective projects are associated with one or moreof said business processes, and with one or more of said tasksrespectively assigned to one or more of said users as defined by theworkflow data of the respective business processes; said manager furtherhas a project control function for controlling the progress of therespective projects in accordance with requests from said users; andsaid project control function is arranged so that this function preparesand displays a task list that lists the tasks assigned to the respectiveusers on the basis of said one or more business processes and said oneor more tasks associated with the respective projects, and so that thisfunction updates said task list for the respective users in accordancewith input indicating the initiation or completion of tasks from therespective users.
 10. A virtual knowledge management system comprising:intensive data administration means for the intensive administration ofvarious types of documents or data that exist in an enterprise; acontrol data editing part which prepares and alters information flowcontrol data involved in the control of the information flow among aplurality of users, and which registers said prepared or alteredinformation flow control data in a memory device; and an informationflow control part which uses said information flow control dataregistered in said memory device to control the flow of said varioustypes of documents or data among a plurality of user terminals used bysaid plurality of users.
 11. The virtual knowledge management systemaccording to claim 10, wherein said control data editing part has autilization authorization editing part which prepares and altersutilization authorization data that indicates the authorization ofrespective users to utilize said various types of documents or data asone type of said information flow control data, and registers theprepared or altered utilization authorization data for each user in saidmemory device, in accordance with requests from specified users; andsaid information flow control part has data utilization control partwhich controls the utilization or operation of the respective users withrespect to various types of documents or data in said data base on thebasis of the utilization authorization data for the respective usersregistered in said memory device.
 12. The virtual knowledge managementsystem according to claim 10, wherein said control data editing part hasa mail communications control data editing part which prepares andalters mail communications control data that indicates desiredlimitations regarding the forwarding of, or reply to, email messagestransmitted from the respective users as one type of said informationflow control data, and associates the prepared or altered mailcommunications control data with email messages transmitted from therespective users, in response to requests from respective users; andsaid information flow control part has a mail communications controlpart which controls the forwarding or reply operations of receivers ofthe respective email messages on the basis of the mail communicationscontrol data associated with the email messages transmitted from saidrespective users.
 13. The virtual knowledge management system accordingto claim 10, wherein said control data editing part has a workflow modelediting part which prepares and alters workflow models relating todesired business processes as one type of said information flow controldata, and registers the prepared or altered workflow models in saidmemory device, in response to requests from specified users; and saidinformation flow control part has a process control part which controlsthe information flow among a plurality of users involved in therespective business processes on the basis of the workflow models of therespective business processes.
 14. The virtual knowledge managementsystem according to claim 13, wherein data relating to the order of workor document flow among a plurality of users involved in respectivebusiness processes is included in said workflow models relating torespective business processes; and said process control part controlsthe order of work or flow of documents among a plurality of usersinvolved in the respective business processes on the basis of said datarelating to the order of work or document flow that is contained in theworkflow models of the respective business processes.
 15. The virtualknowledge management system according to claim 13, further comprising adisplay part which graphically displays a hierarchical structure thatindicates the mutual logical relationship between the business processesand one or more users involved in each of the business processes on thebasis of the data of said workflow models of one or more businessprocesses registered in the memory device.
 16. The virtual knowledgemanagement system according to claim 10, wherein said control dataediting part has a project editing part which prepares and altersproject data relating to projects that include one or more businessprocesses or one or more tasks as one type said information flow controldata, and registers the prepared or altered project data in said memorydevice, in response to requests from specified users; and saidinformation control flow part has a project control part which controlsthe flow of information among a plurality of users involved in therespective projects on the basis of the project data for the respectiveprojects.
 17. The virtual knowledge management system according to claim16, further comprising a display part which graphically displays ahierarchical structure that indicates the mutual logical relationshipsof the projects, one or more business processes or tasks included ineach of the projects and one or more users involved in each of thesebusiness processes or tasks on the basis of project data for said one ormore projects registered in said memory device.
 18. A virtual knowledgemanagement method comprising: intensively administering various types ofdocuments or data present in an enterprise; preparing or alteringinformation flow control data relating to control of the informationflow among a plurality of users; registering said created or alteredinformation flow control data in a memory device; and controlling theflow of said various types of documents or data among user terminalsused by said plurality of users by means of said information flowcontrol data registered in said memory device.
 19. A computer programfor causing a computer to execute a virtual knowledge management methodcomprising: intensively administering various types of documents or datapresent in an enterprise; preparing or altering information flow controldata relating to control of the information flow among a plurality ofusers; registering said created or altered information flow control datain a memory device; and controlling the flow of said various types ofdocuments or data among user terminals used by said plurality of usersby means of said information flow control data registered in said memorydevice.
 20. The virtual knowledge management system according to claim13, wherein said control data editing part has a project editing partwhich prepares and alters project data relating to projects that includeone or more business processes or one or more tasks as one type saidinformation flow control data, and registers the prepared or alteredproject data in said memory device, in response to requests fromspecified users; and said information control flow part has a projectcontrol part which controls the flow of information among a plurality ofusers involved in the respective projects on the basis of the projectdata for the respective projects.